[Feature Request] Build a Less linter that uses the Less parser (Rebuild the parser)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17k
- Forks
- 3.4k
- Avg merge
- 7h 42m
- Merged PRs (30d)
- 26
Description
I am looking for a tool for LESS that does what node-jscs does for JavaScript. It would be useful on project with large teams to enforce a code style throughout the LESS files. I could not find any such tool on npm.
I guess the only technical aspect blocking one from using the LESS Parser from this package to build such a tool is that the Parser discards all whitespace information when building the tree. Otherwise, if one were to build a code style tool one would have to write a new parser for LESS.
I propose an optional setting for the Parser that would make it save the whitespace information in the tree.
Hopefully others out there would use such a tool (LESS code style checker).
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 the Less Parser and how it builds the tree, focusing on where whitespace information is discarded. Define the scope of an optional whitespace-preserving setting and how a style checker would consume that tree; done means the parser can expose whitespace without changing default behavior and the approach is validated for the proposed linter use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- compilers, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100