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

Bug: new rule not supported (lightness-notation) #45

Closed
chrisgrieser opened this issue Dec 29, 2023 · 2 comments
Closed

Bug: new rule not supported (lightness-notation) #45

chrisgrieser opened this issue Dec 29, 2023 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@chrisgrieser
Copy link

chrisgrieser commented Dec 29, 2023

Recently, I started getting this error in the first line of every file:

Unknown rule lightness-notation. stylelintplus: lightness-notation

Looking into it, the rule does exist, but appears to be rather new.

Manually running stylint 16.1.0, reports no issue. I am on stylelint-lsp 2.0.0.


While some delay for new rules in stylint to appear in the stylelint-lsp is no big deal, the fact that a new rule results in errors in the stylelint-lsp is indeed somewhat annoying, and something that you should be able to at least deactivate? Looking at the docs, there seems to be no way to disable the unknown-rule-error, at least as far as I can tell. Maybe the stylelint-lsp could add a small stopgap here or something?

@bmatcuk bmatcuk self-assigned this Dec 31, 2023
@bmatcuk bmatcuk added the bug Something isn't working label Dec 31, 2023
@bmatcuk
Copy link
Owner

bmatcuk commented Dec 31, 2023

Hmm, I would guess that the issue is that stylelint-lsp is using the built-in stylelint dependency, which is on v15, instead of your project's dependency, which must be on 16.1.0. Are you using something other than npm as your package manager?

@chrisgrieser
Copy link
Author

Yeah, I am using npm.

though I just figured out that the error comes from stylelint-config-standard adding lightness-notation, and that explicitly disabling the rule in my config via lightness-notation: null is a simple solution for this already

@chrisgrieser chrisgrieser closed this as not planned Won't fix, can't repro, duplicate, stale Dec 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants