[TODO] Clean up ESLint issues and improve code quality
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 5
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
I'm not sure how much this is still the case, but when the switch was made to ESLint, a lot of ESLint warnings were not addressed. In some cases, the warnings may have been suppressed, but more ideally would be to adopt something like Standard JS, with maybe a few adjustments / accommodations made for Less.js's current code style so that there isn't a change for every single line of code.
Contributor guide
No contributing guide indexed for this repository
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 the current ESLint setup and the warnings or suppressions referenced in this issue. Compare the existing rules with Standard JS and identify the Less.js code-style accommodations required; done means an agreed rule set and a clean, maintainable lint result without unnecessary line-by-line changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100