-
Notifications
You must be signed in to change notification settings - Fork 4
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
bug(config): .stylintrc (with groupOutputByFile) doesn't work #11
Comments
Same issue here, most of the time i get parse error in the console. Any preferred reporter config that definitely works? |
This isn't matching because the output includes the filename at the very beginning — if you turn That said, this should really be able to handle that case, so I'll work on it. Thank you for the report @Kristinita |
Just wanted to give an update on this: the plugin does not work well in many cases, I have opened a PR with stylint to help resolve this (SimenB/stylint#454). The root issue is that parsing stylint warnings and errors is difficult, because there is no way for this plugin to dictate the format of those errors, and their format can vary drastically between versions and configurations. Once the PR above has been merged, it should be possible to get this plugin working better. 🙏 |
1. Summary
Options from
.stylintrc
doesn't work for me.#9 — possibly related issue.
2. Environment
3. Configuration
.stylintrc
:SashaStylus.styl
:User/SublimeLinter.sublime-settings
:4. Steps to reproduce
I reproduce the problem in a version of Sublime Text without plugins and user settings.
I install SublimeLinter and SublimeLinter-contrib-stylint → I restart Sublime Text → I open Sublime Text console → I open
SashaStylus.styl
.5. Expected behavior
If Stylint CLI:
6. Actual behavior
stylint(ok)
, no gutter marks.Warnings show in console.
Thanks.
The text was updated successfully, but these errors were encountered: