Nested-lite scheme for walking
- Dominant language
- JavaScript
- Stars
- 89
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
In explanation https://github.com/bem-sdk-archive/bem-walk/issues/81 and https://github.com/bem-site/bem-forum-content-ru/issues/1100
```
block/tech
block/_mod/tech
block/_mod_val/tech
block/__elem/tech
block/__elem/_mod/tech
block/__elem/_mod_val/tech
```
Tech endpoint file path (or dir example: i18n).
Information about the entity lies in the path of the directory
```
block/__elem/_mod_val/
```
If it is associated with the task #243 , you get the result
```
block/tech
block/@platform.tech
block/_mod_val/tech
block/_mod_val/@platrorm.tech
block/__elem/tech
block/__elem/@platform.tech
block/__elem/_mod_val/tech
block/__elem/_mod_val/@platform.tech
```
Example CtrlP
Contributor guide
Research direction
Read the linked explanations in bem-walk issue #81 and bem-forum-content-ru issue #1100, then compare their nested-lite path examples with the walking behavior in bem-sdk. Confirm how the scheme relates to task #243 and the expected endpoint paths; done means the walker supports the documented block, element, modifier, value, and platform forms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100