You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is somewhat related to #19, but since v2 has been released, this likely concerns the new ignoreProperties configuration option.
The main use-case if for those using styled-components/emotion, where the use of stylelint-processor-styled-components will insert placeholders in the code, i.e. -styled-mixin0: $dummyValue. The $dummyValue value can be easily ignored by using a regex for ignoreValue config option. However, this isn't the same for the invalid property -styled-mixin0, because the processor appends an incremental number to the end of the property.
This means it is unnecessarily verbose to do this:
And this is not a safe way to fix the issue, since the number is arbitrary. What if we allow ignoreProperties to accept Array<string | RegExp>? By extension, we might want to extend the ignoreValue as well, so that it not only accepts string | RegExp but also Array<string | RegExp>.
I am happy to create a PR for this if necessary: but would love to hear your opinion on this.
The text was updated successfully, but these errors were encountered:
This is somewhat related to #19, but since v2 has been released, this likely concerns the new
ignoreProperties
configuration option.The main use-case if for those using styled-components/emotion, where the use of stylelint-processor-styled-components will insert placeholders in the code, i.e.
-styled-mixin0: $dummyValue
. The$dummyValue
value can be easily ignored by using a regex forignoreValue
config option. However, this isn't the same for the invalid property-styled-mixin0
, because the processor appends an incremental number to the end of the property.This means it is unnecessarily verbose to do this:
And this is not a safe way to fix the issue, since the number is arbitrary. What if we allow
ignoreProperties
to acceptArray<string | RegExp>
? By extension, we might want to extend theignoreValue
as well, so that it not only acceptsstring | RegExp
but alsoArray<string | RegExp>
.I am happy to create a PR for this if necessary: but would love to hear your opinion on this.
The text was updated successfully, but these errors were encountered: