Skip to content
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

--rd flag makes stylelint not to report any violations at all #4100

Closed
sobolevn opened this issue Jun 5, 2019 · 4 comments
Closed

--rd flag makes stylelint not to report any violations at all #4100

sobolevn opened this issue Jun 5, 2019 · 4 comments
Labels
status: needs clarification triage needs clarification from author

Comments

@sobolevn
Copy link

sobolevn commented Jun 5, 2019

Clearly describe the bug

Reproduction:

/* index.css */
.empty{}

Running 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.

Expected output:

  1. block-no-empty violation
  2. Unused property-no-unknown comment violation

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

@sobolevn
Copy link
Author

sobolevn commented Jun 5, 2019

Original issue: wemake-services/wemake-vue-template#608

@hudochenkov
Copy link
Member

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.

Unused property-no-unknown comment violation

I can't reproduce it. With stylelint@10.1.0 I see the report:

$ npx stylelint index.css --report-needless-disables

index.css
unused rule: property-no-unknown, start line: 2, end line: 2

@hudochenkov
Copy link
Member

Closing because of no response from the author.

@sobolevn
Copy link
Author

I would say that this issue: #4076 tracks the feature I am interested in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: needs clarification triage needs clarification from author
Development

No branches or pull requests

2 participants