Closed fyodorvi closed 6 years ago
Same here. (Webstorm 11.0.3, sass-lint 1.5.0)
Although warnings are displayed as they should.
Update: Could it be that sass-lint library should be run with '-q' flag, so process would exit with code 0 instead? I haven't tested, because I'm pretty new to webstorm ide and I'm not so familiar with developing/debugging plugins :)
I modified my local copy of sass-lint.js to ignore the -q flag (and treat it as always enabled) and the sass-lint plugin worked for me. Passing through -q should work, given this experiment.
We are now running two different rulesets to bypass this bug. -.sass-lint-dev.yml has only warnings enabled and is used for development in webstorm. -.sass-lint.yml has errors enabled for the build-process.
Yeah this is totally broken from my perspective. I will just run with gulp if this is the expected behavior, the ESLint plugin should be the model of behavior this plugin follows by default: https://github.com/idok/eslint-plugin
This plugin would be nothing short of amazing if worked the way everyone on here wants it to. Anything we can do to make this happen? I'm not exactly fluent in java but if someone is willing to point me into the right direction..
Yep, same problem here
Same here :(
Same problem here
Looks like this is not relevant with latest version, please reopen if needed
We have strict linting rules on our project, they all are errors instead of warning, so pre-commit hook may fail on error. But plugin acts strange in this case: instead of highlighting errors it shows balloon with almost no information: "Error: 6 errors were detected in ...".
It doesn't make any sense.