CSS checker enhancement request; output full details of each error’s location, including errors inside @imports
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 250
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
In the CSS checker error messages should also (i) include the line number within @imported files if their content is also being scanned, (ii) the filename of the file where the error is found, and (iii) the line number of the current @import within the main file, as is being done currently.
The filename should be omitted if this is the main file.
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 locating the CSS checker’s error-formatting and @import scanning entry points. Trace how errors from imported files currently retain the current @import line, then verify output includes the imported filename and its internal line number while omitting the filename for the main file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100