We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hey there :) I've just tried to add stylelint-stylus to our codebase and came across a bug in the semicolon rule.
using "stylus/semicolon": "always", the semicolon is added after the single line comment
before: height: 40px // comment
height: 40px // comment
after: height: 40px // comment;
height: 40px // comment;
this causes the linter to still throw an error, as the semicolon is not part of the code, but part of the comment
The text was updated successfully, but these errors were encountered:
Thank you for posting the issue! It may be a bug in stringify of postcss-styl.
stringify
Sorry, something went wrong.
possibly. I tried to debug it and was confused about the comment not showing up in the AST
And there has a same problem unexcepted semicolon with stylelint-config-recess-order plugin.
for example:
body color red font-weight 500
with vscode autosave format will get the result: more semicolon appear which property has be reordered
body font-weight 500; color red
No branches or pull requests
Hey there :)
I've just tried to add stylelint-stylus to our codebase and came across a bug in the semicolon rule.
using "stylus/semicolon": "always", the semicolon is added after the single line comment
before:
height: 40px // comment
after:
height: 40px // comment;
this causes the linter to still throw an error, as the semicolon is not part of the code, but part of the comment
The text was updated successfully, but these errors were encountered: