stylelint-declaration-use-variable

:warning: This project is not actively maintained. Please use stylelint-declaration-strict-value :warning:

A stylelint plugin that check the use of scss, less or custom css variable on declaration. Either used with '$', map-get(), '@' or 'var(--var-name)'.

Installation

npm install stylelint-declaration-use-variable

Be warned: v0.2.0+ is only compatible with stylelint v3+. For earlier version of stylelint, use earlier versions of this.

Usage

Add it to your stylelint config plugins array, then add "declaration-use-variable" to your rules, specifying the property for which you want to check the usage of variable.

Like so:

1// .stylelintrc
2{
3  "plugins": [
4    "stylelint-declaration-use-variable"
5  ],
6  "rules": {
7    // ...
8    "sh-waqar/declaration-use-variable": "color",
9    // ...
10  }
11}

Multiple properties

Multiple properties can be watched by passing them inside array. Regex can also be used inside arrays.

1// .stylelintrc
2"rules": {
3  // ...
4  "sh-waqar/declaration-use-variable": [["/color/", "z-index", "font-size"]],
5  // ...
6}

Regex support

Passing a regex will watch the variable usage for all matching properties. This rule will match all CSS properties while ignoring Sass and Less variables.

1// .stylelintrc
2"rules": {
3  // ...
4  "sh-waqar/declaration-use-variable": "/color/",
5  // ...
6}

Options

Passing ignoreValues option, you can accept values which are exact same string or matched by Regex

1// .stylelintrc
2"rules": {
3  // ...
4  "sh-waqar/declaration-use-variable": [["/color/", "font-size", { ignoreValues: ["transparent", "inherit", "/regexForspecialFunc/"] }]],
5  // ...
6}

Details

Preprocessers like scss, less uses variables to make the code clean, maintainable and reusable. But since developers are lazy they might get a chance to miss the use of variables in styling code and that kinda sucks.

1$some-cool-color: #efefef;
2
3.foo {
4    display: inline-block;
5    text-align: center;
6    color: #efefef; // Wait a min! there should be a variable.
7}

Supported scss variables

Scss variables using '$' notation and map-get are supported

1// Simple variables
2$some-cool-color: #efefef;
3$some-integer: 123;
4$some-pixels: 4px;
5
6color: $some-cool-color;
7
8// Using map-get
9$cool-colors: (
10    blue: #3ea1ec,
11    red: #eb5745,
12);
13
14color: map-get($cool-colors, blue);
15

Supported color functions

If you plan to level-up the usage of your variables by the usage of fancy color-functions - you can!

Instead of a direct variable usage like this:

1$white: #fff;
2
3.foo {
4  color: $white;
5}

You could also do things like:

1.foo {
2  color: color($white shade(10%));
3}

This will still be seen as a valid code by the plugin. As a side-note, it doesn't matter what kind of variable-syntax you are using in the color function itself - if the line starts with color( then it is seen as valid.

If you contribute and wonder about the check for color( - it couldn't be done via regex because not only values will be passed to the plugin, but also property names. For some reason, the plugin just dies if you start extending the regex to look for "color". So it must be done via extra-if-check.