import-js / import-js/eslint-plugin-import
"import/order" Several ideas to implement
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5.9k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
Hello, i want files ending with ./*.css to be LAST in sibling group, so to my mind there are 2 potential ways to solve this:
1. In pathGroups you need to add property disabling newlines-between for this pathGroups (and same for groups)
2. If we miss position (so our pathGroups become the part of passed "group"), plugin should be able to order something like this - "order": "begin" | "end"
Please implement one of these features. Or if there are workaround for my situation, share please.
Not realted to my issue ideas:
1. Add "name" property for pathGroups to be able to order other pathGroups relatively to named pathGroups
2. Add possibility to order "type" imports as your main "gropus", for example i have in "groups": ["external", "internal", "type"], so i want to sort "type" group firstly external and then internal
Contributor guide
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 import/order rule's handling of pathGroups, groups, and newlines-between. Compare the two proposed directions—disabling newlines-between for a pathGroup or supporting begin/end ordering—and identify which behavior can be specified and tested consistently. Done means one requested ordering behavior is implemented with coverage for CSS sibling groups.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100