Consider adding ESLintBear
Open
- Dominant language
- JavaScript
- Stars
- 18
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
Current linters don't catch a lot of issues in the code, so it may be beneficial to add ESLintBear or tweak configuration of existing ones to make PRs less painful and improve code quality in general.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by inspecting the repository's current linter setup and identifying which issues it misses. Compare adding ESLintBear with adjusting the existing linters, then determine how linting runs for pull requests. Done means an agreed approach is implemented and PR checks catch the targeted code-quality problems.
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
- 20/100