Review ESLint issues
Open
client
enhancement
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Plan is to check through eslint issues and eventually use it properly. Currently it has 2200+ things it wants us to change
Contributor guide
Research direction
No files, entry points, or tests are identified. Start by locating the ESLint configuration and running the project's lint command to inspect the 2,200+ reported issues. The scope and completion criteria need to be narrowed before work can begin.
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
- 20/100