Disable case value-keyword-case for composes #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #7, #13
Just checking what it takes, whether it make sense or not.
While this "solves" the issue with classes used with
composes
. This does not solve the one with@value
.Since
@value
can be used in a wide range of properties, we don't have much solutions here.Also we can see that disabling
selector-class-pattern
was necessary locally.The CSS modules spec don't enforce a particular case, so this config won't disable
selector-class-pattern
. It's out of scope.The whole benefit of this change is quite debatable, some per projects overrides will always be needed.
One would still need to:
selector-class-pattern
locally@value
or build a unmaintainable list of ignored properties