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
Describe the issue. Is it a bug or a feature request (new rule, new option, etc.)?
Now, declaration-empty-line-before doesn't ignores shared-line comments if it's in a selector. Probably relates to #2237.
Which rule, if any, is this issue related to?
declaration-empty-line-before except: ["after-declaration", "first-nested"] ignore: ["after-comment']
declaration-empty-line-before
What CSS is needed to reproduce this issue?
.class { /* comment */ display: block; }
What stylelint configuration is needed to reproduce this issue?
e.g.
{ "declaration-empty-line-before": ["always", { except: [ "after-declaration", "first-nested" ], ignore: [ "after-comment" ] }] }
Which version of stylelint are you using?
8.0.0
How are you running stylelint: CLI, PostCSS plugin, Node API?
CLI
Does your issue relate to non-standard syntax (e.g. SCSS, nesting, etc.)?
No.
What did you expect to happen?
No warnings to be flagged.
What actually happened (e.g. what warnings or errors you are getting)?
The following warnings were flagged:
48:9 ✖ Expected empty line before declaration declaration-empty-line-before
The text was updated successfully, but these errors were encountered:
@agordeev-zz Thanks for using the template. This should be fixed in the upcoming 8.1.0 release.
8.1.0
Sorry, something went wrong.
No branches or pull requests
Now, declaration-empty-line-before doesn't ignores shared-line comments if it's in a selector. Probably relates to #2237.
declaration-empty-line-before
except: ["after-declaration", "first-nested"]
ignore: ["after-comment']
e.g.
8.0.0
CLI
No.
No warnings to be flagged.
The following warnings were flagged:
The text was updated successfully, but these errors were encountered: