eslint-config
eslint-config copied to clipboard
🍰 Lint feature-sliced concepts by existing eslint plugins
# Description Разбиты на отдельные конфиги slice и layers boundaries. Пока сохранен slices-and-layers-boundaries (потом нужно будет написать мерж конфигов) Добавлены тесты для slices-and-layers-boundaries. # Reference #45 # Checks - [x]...
### Description Should work for each rule - [ ] `imports-order` - [ ] `layers-slices` - [ ] `public-api` ### Reference ```js // Pass import { ... } from "entities/user";...
https://github.com/feature-sliced/eslint-config/discussions/55#discussioncomment-1931162
### Description - [ ] Segments (in shared and in slices) should follow the next rule: > `ui` => `model` => `api` => `lib` => `config` - [ ] Ideally:...
### Description Should work for each rule - [ ] `imports-order` - [ ] `layers-slices` - [ ] `public-api` ### Reference ```js // Pass import { ... } from "entities/user";...
Add remained options from #22 - [ ] Option 4. Customize impl of configs > - [ ] "I want to enable `shared/styles` in public-api linting" > - [ ]...
- [ ] Optimize built config? https://github.com/shashkovdanil/clean-publish#readme https://github.com/effector/eslint-plugin/blob/master/package.json#L28 - [ ] Rename "index.js" to "recommended"? - [ ] More explicit "public" and "private" utils For ignoring redundant libs 
## Problem - Compatibility (better decide "too earlier", than "too late") - A lot of variations of rules for same concept > PublicAPI: `private-imports`, `segments-api`, `relative-imports`, `unified-api`, ... > Decomposition:...