denisraslov/stylelint-value-no-exposed-custom-properties

A stylelint rule to disallow usage of exposed custom properties

stylelint-value-no-exposed-custom-properties's Issues

can you make, that variables changes automaticaly, not warnings in terminal

Unexpected errors when using alias

When using aliases, the plugin requires to use the latest alias variable. While both should be allowed.

For insatnce:
:root {
--my-color-variable: #FF0000;
--my-alias-variable: var(--my-color-variable);
}

.my-element {
// This i allowed which is totally fine
background-color: var(--my-alias-variable);
}

.my-element {
// This is not allowed. The plugins requires that only the alias is used, while both are acceptable use of the variables
background-color: var(--my-color-variable);
}

Value matching behaviour

Hi! Thanks for the plugin.

Can you please explain, why default matching behaviour is value.includes(property)?

stylelint-value-no-exposed-custom-properties/index.js

Line 25 in 52779ac

if (value.includes(property)) return i;

It seems very strange, because when I got some custom property like --z-index-header: 1 in my CSS, plugin suggests me to replace every value that includes 1 with this custom property, i.e. The value (or a part of it) should be presented as a custom property: "1.125rem" is "--z-index-header".

Is include used to detect exposed values in shorthand properties like background? Maybe we should split property value by space character and check every part of it instead of checking the whole value?

Not compatible with latest Stylelint Versions

Any chance we can get this updated to support newer versions?