-
-
Notifications
You must be signed in to change notification settings - Fork 930
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
Fix rule-selector-property-disallowed-list
secondary options
#6688
Comments
@clshortfuse Thank you for the report with the detailed reproduction! The rule's
The rule's primary option type is an object, not an array:
I've labeled the issue as ready to implement. Please consider contributing if you have time. There are steps on how to fix a bug in a rule in the Developer guide. |
rule-selector-property-disallowed-list
secondary options
Small nitpick, it seems that the |
Good catch. Please open a PR to fix the typo on the doc. |
Hi @ybiquitous, is anyone working on this issue? If not, I'm interested! |
@cherieliu Thank you for your proposal. But unfortunately, PR #6723 is opened. 😅 |
What steps are needed to reproduce the bug?
Try to add a message parameter to
rule-selector-property-disallowed-list
.See REPL: https://stylelint.io/demo#N4Igxg9gJgpiBcICGACYLIBsICd4pxigG4UBfAHQDtqQAaEAZwE8qAXJADwXEcfvAQqAMwCWAcx7BqKFBRA4ArphiN5+aVVmz5SlQFpGMFWDa59ABxwQLMHG2b6ooxkkzYA7kX2YXbdSgA2jLaspqhofJIAcGC2DjydHIgAPQAtkg44qJUKfIAunQhEckpwhAQeQiljKIAXjBVxdpkRVol4SXJaaqu4jAB8gByEGwobp5E8s2ylO2y+SFzZCBkQA
Removing the array (and the message) with an object works:
https://stylelint.io/demo#N4Igxg9gJgpiBcICGACYLIBsICd4pxigG4UBfAHQDtqQAaEAZwE8qAXJADwXEcfvAQqAMwCWAcx7BqKFBRA4ArphiN5+aVVmz5SlQFpGMFWDa59ABxwQLMHG2b6ooxkkzYA7kX2YXbdXJa2rKawcHySAEA2vJYuPJ0ciAA9AC2SDjiolTJ8gC6dDJhOinCEBC5CEnJjKIAXjCVRcGUQa1kIGRAA
What Stylelint configuration is needed to reproduce the bug?
How did you run Stylelint?
npx stylelint test.css
Which version of Stylelint are you using?
15.2.0
What did you expect to happen?
Should support messages
What actually happened?
Rule is ignored
Does the bug relate to non-standard syntax?
No response
Proposal to fix the bug
Check code with
declaration-property-value-disallowed-list
which does work.The text was updated successfully, but these errors were encountered: