Repository navigation
processString error format #4
Description
Activity
There are 4 types of errors in CSScomb based on who is responsible for breaking stuff:
- User (e.g. unacceptable value in config, something weird in
comb.use()) - Third-party developer
- Parser
- Linter
processStringmethod throws only parsing errors, so they have nothing to do with linting.
What you need for a linter (as I think) is a separate methodlintString(see csscomb/csscomb.js#261) that will return a list of errors:[ { file: "css/asd.css", line: 2, column: 9, message: "Missing semicolon" }, { file: "css/qwe.css", line: 2, column: 11, message: "Extra space after colon" } ]
And inside your plugin you can decide yourself how you'll print those errors.
- User (e.g. unacceptable value in config, something weird in
yep, you are right. separate method is what I need. it will be better in performance too.
errorshould havefileproperty which should be relative path to file:errorshould have clearmessageproperty without note about path to current file or csscomb and gonzales versions.If we csscomb core will throw error in this format then linters will can collect invalid files with errors in and output the result it at the end of linting all the files like this