Closed chrisblossom closed 5 years ago
To me it looks like a stylelint issue, check this: https://github.com/stylelint/stylelint/issues/1153
Remember that you can check what stylelint says by running it manually when you see something odd in sublime stylelint. It helps a bit.
When stylelint handles that error situation better, I'd assume this repository can also be fixed to handle it a bit better.
@Arkkimaagi Thanks for the response. Actually running it via CLI was the first thing I tried and it works as expected.
Here is my css linting command: stylelint --syntax scss 'src/**/*.scss'
I suspect the issue is this plugin not specifying --syntax scss and parsing the files as plain css. https://github.com/stylelint/stylelint/blob/master/docs/user-guide/css-processors.md#parsing-non-standard-syntax
Any suggestions on how to add --syntax scss
to further test?
I have no perfect solution, but you can try my hack if you're feeling adventurous. https://github.com/kungfusheep/SublimeLinter-contrib-stylelint/issues/29
Even tho I talk only about LESS support in it, I tried to code it to support scss and sss file formats too.
That solved the issue. Thanks for your help. Hopefully an iteration of your self-called "hack" gets implemented.
Since this issue isn't solved I am going to keep it open.
Does anyone know what I am doing wrong here? Below is the sublimelinter debug output.
Thank you!