import-js / import-js/eslint-plugin-import
import/order: needs a champion?
- Dominant language
- JavaScript
- Stars
- 5.9k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
@jfmengels / @ljharb: what do y'all think of spinning `import/order` (and maybe more/all the pure style-guide rules) out into a separate plugin?
There is clearly an enthusiastic user base, but I am not a member thereof and so I think it's frustrating for everyone when I basically just don't get involved, and I don't have the bandwidth already to manage the static analysis stuff (which I do use and am passionate about).
Thoughts?
Practically, I think we'd move the current implementation either back to @jfmengels' project or to some new project (not sure whose, in that case) and then deprecate here with a note to migrate to the new separate plugin, and remove in v3.
Contributor guide
Research direction
Start by reading the issue discussion about spinning out import/order and other pure style-guide rules. No files or tests are named; first establish ownership and whether a separate plugin is agreed upon. Done would require a decided migration, deprecation, and removal plan, but the issue currently has no decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, javascript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100