New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Webstorm error: StreamException: : input contained no data
#1
Comments
please try explicitly setting the sass-lint.yml in the settings |
Ok seems to work. Now it seems the linter gets triggered when ever I type and not just on save. For example when i type:
|
I researched a bit, |
Hi, I have both the package.json file (without any reference to sass-lint though) and a .sass-lint.yml file. Anyway with the latest plugin update I don't experience the first problem anymore. I still get the parsing error before hitting save. I wonder if those file in groot.js is something related to sass-lint (see sasstools/sass-lint#456). If so, maybe it'd be an option to suppress the parsing error until they update the AST. |
Would you mind posting a sample of the code that this is failing on @dwightjack ? I haven't used this plugin yet but if it's linting as you type it will often throw parse errors on incomplete code, once the block is complete though it should lint fine. There's an update for sass-lint coming hopefully today that will report these parse errors specifically as lint errors so it shouldn't be as frustrating as the unhandled errors are at the moment. If the code is complete and you're still encountering a parse error then unfortunately there's still a few cases where you will see this with the AST we use in its current state. Specifically most types of interpolation or even files using hard tabs. Hopefully these will be sorted soon. It would be helpful if you could post these types of issues on the sass-lint repo itself so we can better keep track of them! Thanks! |
Hi with material UI theme i'm getting the following error:
If you need any further detail, just ping me :)
The text was updated successfully, but these errors were encountered: