Evaluate new rules in ESLint 9
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 9
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Describe the issue
When we implemented #155 we made some effort to avoid introducing rules that were stricter than our existing ruleset to try to reduce churn on clients uptaking the new version. Similar to #134 we should circle back to see if there are any rules that we disabled that we want to enable.
Step 1 is figuring out how to see a list of those rules. Perhaps scanning ESLint's changelogs and blog posts? Maybe a good subset to start with would be ensuring we enable the "recommended" rules (or have good reasons to disable them).
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 reviewing issues #155 and #134, then scan ESLint 9 changelogs and blog posts for rules that were disabled or became recommended. Compare those findings with the current ruleset and decide which recommended rules have sufficient justification to enable; done means the rule choices and reasons are recorded and the style guide configuration reflects the decision.
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
- 35/100