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
Clearly describe the bug
Reproduction:
/* index.css */ .empty{}
Running npx stylelint index.css:
npx stylelint index.css
1:8 ✖ Unexpected empty block block-no-empty
Then, let's add an unused ignore:
/* index.css */ /* stylelint-disable-next-line property-no-unknown */ .empty{}
And run npx stylelint --rd index.css. No output will be received. It just passes.
npx stylelint --rd index.css
Expected output:
block-no-empty
property-no-unknown
What stylelint configuration is needed to reproduce the bug?
{ "rules": { "block-no-empty": true } }
Which version of stylelint are you using?
latest: 9.10.1
The text was updated successfully, but these errors were encountered:
Original issue: wemake-services/wemake-vue-template#608
Sorry, something went wrong.
Thanks for the report and for using the template.
block-no-empty violation
When --report-needless-disables stylelint reports only needless disables, and no other violations. We have an open issue to change that.
--report-needless-disables
Unused property-no-unknown comment violation
I can't reproduce it. With stylelint@10.1.0 I see the report:
stylelint@10.1.0
$ npx stylelint index.css --report-needless-disables index.css unused rule: property-no-unknown, start line: 2, end line: 2
Closing because of no response from the author.
I would say that this issue: #4076 tracks the feature I am interested in.
No branches or pull requests
Reproduction:
Running
npx stylelint index.css
:Then, let's add an unused ignore:
And run
npx stylelint --rd index.css
. No output will be received. It just passes.Expected output:
block-no-empty
violationproperty-no-unknown
comment violationlatest: 9.10.1
The text was updated successfully, but these errors were encountered: