fullstack-development / fullstack-development/front-end-best-practices
Форматирование размещения импортов
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 336
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
Думаю, следует дополнить стандарт примерами для:
- использования путей с алиасами;
- что делать в случае если импорт используется только для правки порядка импорта ресурсов сборщиком (при использовании bem компонент должен быть импортирован раньше модификаторов, которые лежат глубже).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked section 1.17 in JS/README.md. Add standard examples covering aliased import paths and imports used only to enforce resource ordering, including the BEM component-before-modifier case. Done means both requested situations are clearly documented in the standard.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100