Investigate eslint config inspector
Open
Nobody has claimed this yet.
triage
- Dominant language
- JavaScript
- Stars
- 9
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
I came across this interesting package ESLint Config Inspector. It's a UI for visualizing a config: what rules it contains and what files it applies to.
We should play around with it consider incorporating into our workflows:
- link to it from docs as something to use when enabling javascript-styleguide on a repo to validate you did it right?
- run it on some client repos and see if it reveals anything interesting like unlinted files or disabled rules?
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 with the linked ESLint Config Inspector and the javascript-styleguide documentation or workflow guidance. Try it with the style guide and client repositories, then document whether it exposes unlinted files or disabled rules and whether a documentation link or workflow change is justified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100