this post was submitted on 10 Apr 2024
10 points (100.0% liked)
Cool GitHub Projects
1212 readers
1 users here now
Wormhole
Icon base by Caro Asercion under CC BY 3.0 with modifications to add a gradient
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It is, but I'd specifically like a rule that enforces this style of import over aliased imports. I.e. when importing a package, the order of importance is:
Current plugin is just about force use aliases instead of relative paths (and back for deprecated aliases).
If you need to sort imports, you may try rule
simple-import-sort/imports
from https://github.com/lydell/eslint-plugin-simple-import-sort It is very flexible, so you may customize your own groups. For instance, you may group aliases in one group and relative imports to another group. Check their docsSorry, maybe I'm not being clear - I'm not talking about sorting. I'm talking about an ESLint rule that flags alias imports that can be expressed as relative subdirectory imports, but flags other imports that could have been alias imports. Does that make sense?
Examples: