[Feature] ignore pattern for values #14
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
any chance we can get some action on this PR? It'd be really handy to have as a temporary solution until scss/less preprocessing is supported |
|
The repo might be dead, but I still want to up this one. I've just migrated to stylelint with a preconfigured set of strict rules, and I have to disable this rule. 😢 |
|
Thanks @zabute! I'm merging it, and will modify it a little. |
|
I also added |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This introduces a new option:
ignoreValuewhich takes a Regular Expression and prevents Invalid/Parse warnings for values that match the pattern. Property warnings will still be reported.It should help with issues like #10 and #11. Another use case is one I came across when building stylelint-processor-glamorous: The processor replaces javascript expressions with a placeholder value before flushing the css to stylelint. This causes spurious Invalid value warnings. I thought about taking care of it within the processor but looking at #10 & #11, I thought it would be best for this validator to handle it.
PR includes: