Comments misplaced
Open
Nobody has claimed this yet.
feature request
low priority
up-for-grabs
- Dominant language
- JavaScript
- Stars
- 17k
- Forks
- 3.4k
- Avg merge
- 7h 42m
- Merged PRs (30d)
- 26
Description
Less.js Version: 3.11.1
/** a */
.modal {
/** b */
&-header {
font-size: 12px;
}
/** c */
&-title {
font-size: 12px;
}
Output:
/** a */
.modal {
font-size: 12px;
/** b */
/** c */
}
.modal-header {
font-size: 12px;
}
.modal-title {
font-size: 12px;
}
I think it should output:
/** a */
.modal {
font-size: 12px;
}
/** b */
.modal-header {
font-size: 12px;
}
/** c */
.modal-title {
font-size: 12px;
}
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 reproducing the Less.js 3.11.1 example from the issue and compare its generated CSS with the expected output. Trace the compiler's handling of comments around nested selectors; done means comments b and c appear immediately before .modal-header and .modal-title rather than inside .modal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 42/100