value-keyword-case

Specify lowercase or uppercase for keywords values.

a { display: block; }
/**              ↑
 *    These values */

This rule ignores <custom-idents> of known properties. Keyword values which are paired with non-properties (e.g. $vars and custom properties), and do not conform to the primary option, can be ignored using the ignoreKeywords: [] secondary option.

The [fix option](../../../docs/user-guide/usage/options.md#fix) can automatically fix all of the problems reported by this rule.

declaration-colon-space-after

Require a single space or disallow whitespace after the colon of declarations.

a { color: pink }
/**      ↑
 * The space after this colon */

The [fix option](../../../docs/user-guide/usage/options.md#fix) can automatically fix all of the problems reported by this rule.

selector-type-no-unknown

Disallow unknown type selectors.

unknown {}
/** ↑
 * This type selector */

This rule considers tags defined in the HTML, SVG, and MathML specifications to be known.

function-comma-space-after

Require a single space or disallow whitespace after the commas of functions.

a { transform: translate(1, 1) }
/**                       ↑
 * The space after this comma */

The [fix option](../../../docs/user-guide/usage/options.md#fix) can automatically fix all of the problems reported by this rule.

value-keyword-case

Specify lowercase or uppercase for keywords values.

a { display: block; }
/**              ↑
 *    These values */

This rule ignores <custom-idents> of known properties. Keyword values which are paired with non-properties (e.g. $vars and custom properties), and do not conform to the primary option, can be ignored using the ignoreKeywords: [] secondary option.

The [fix option](../../../docs/user-guide/usage/options.md#fix) can automatically fix all of the problems reported by this rule.

MD022 - Headers should be surrounded by blank lines

Tags: headers, blank_lines

Aliases: blanks-around-headers

This rule is triggered when headers (any style) are either not preceded or not followed by a blank line:

# Header 1
Some text

Some more text
## Header 2

To fix this, ensure that all headers have a blank line both before and after (except where the header is at the beginning or end of the document):

# Header 1

Some text

Some more text

## Header 2

Rationale: Aside from aesthetic reasons, some parsers, including kramdown, will not parse headers that don't have a blank line before, and will parse them as regular text.

declaration-block-semicolon-space-after

Require a single space or disallow whitespace after the semicolons of declaration blocks.

a { color: pink; top: 0; }
/**            ↑
 * The space after this semicolon */

This rule ignores:

• semicolons that are preceded by Less mixins
• the last semicolon of declaration blocks

Use the block-closing-brace-*-before rules to control the whitespace between the last semicolon and the closing brace instead.

The [fix option](../../../docs/user-guide/usage/options.md#fix) can automatically fix all of the problems reported by this rule.

declaration-block-trailing-semicolon

Require or disallow a trailing semicolon within declaration blocks.

a { background: orange; color: pink; }
/**                                ↑
 *                    This semicolon */

The trailing semicolon is the last semicolon in a declaration block and it is optional.

This rule ignores:

• Less mixins
• trailing // comments
• declaration blocks containing nested (at-)rules

The [fix option](../../../docs/user-guide/usage/options.md#fix) can automatically fix all of the problems reported by this rule.

function-comma-space-after

Require a single space or disallow whitespace after the commas of functions.

a { transform: translate(1, 1) }
/**                       ↑
 * The space after this comma */

The [fix option](../../../docs/user-guide/usage/options.md#fix) can automatically fix all of the problems reported by this rule.

function-comma-space-after

Require a single space or disallow whitespace after the commas of functions.

a { transform: translate(1, 1) }
/**                       ↑
 * The space after this comma */

The [fix option](../../../docs/user-guide/usage/options.md#fix) can automatically fix all of the problems reported by this rule.

selector-type-no-unknown

Disallow unknown type selectors.

unknown {}
/** ↑
 * This type selector */

This rule considers tags defined in the HTML, SVG, and MathML specifications to be known.

selector-type-no-unknown

Disallow unknown type selectors.

unknown {}
/** ↑
 * This type selector */

This rule considers tags defined in the HTML, SVG, and MathML specifications to be known.

value-keyword-case

Specify lowercase or uppercase for keywords values.

a { display: block; }
/**              ↑
 *    These values */

This rule ignores <custom-idents> of known properties. Keyword values which are paired with non-properties (e.g. $vars and custom properties), and do not conform to the primary option, can be ignored using the ignoreKeywords: [] secondary option.

The [fix option](../../../docs/user-guide/usage/options.md#fix) can automatically fix all of the problems reported by this rule.

For more information visit Source: http://eslint.org/docs/rules/

selector-type-no-unknown

Disallow unknown type selectors.

unknown {}
/** ↑
 * This type selector */

This rule considers tags defined in the HTML, SVG, and MathML specifications to be known.

MD032 - Lists should be surrounded by blank lines

Tags: bullet, ul, ol, blank_lines

Aliases: blanks-around-lists

This rule is triggered when lists (of any kind) are either not preceded or not followed by a blank line:

Some text
* Some
* List

1. Some
2. List
Some text

To fix this, ensure that all lists have a blank line both before and after (except where the block is at the beginning or end of the document):

Some text

* Some
* List

1. Some
2. List

Some text

Rationale: Aside from aesthetic reasons, some parsers, including kramdown, will not parse lists that don't have blank lines before and after them.

Note: List items without hanging indents are a violation of this rule; list items with hanging indents are okay:

* This is
not okay

* This is
  okay

no-descending-specificity

Disallow selectors of lower specificity from coming after overriding selectors of higher specificity.

#container a { top: 10px; } a { top: 0; }
/** ↑                           ↑
 * The order of these selectors represents descending specificity */

Source order is important in CSS, and when two selectors have the same specificity, the one that occurs last will take priority. However, the situation is different when one of the selectors has a higher specificity. In that case, source order does not matter: the selector with higher specificity will win out even if it comes first.

The clashes of these two mechanisms for prioritization, source order and specificity, can cause some confusion when reading stylesheets. If a selector with higher specificity comes before the selector it overrides, we have to think harder to understand it, because it violates the source order expectation. Stylesheets are most legible when overriding selectors always come after the selectors they override. That way both mechanisms, source order and specificity, work together nicely.

This rule enforces that practice as best it can, reporting fewer errors than it should. It cannot catch every actual overriding selector, but it can catch certain common mistakes.

How it works

This rule looks at the last compound selector in every full selector, and then compares it with other selectors in the stylesheet that end in the same way.

So .foo .bar (whose last compound selector is .bar) will be compared to .bar and #baz .bar, but not to #baz .foo or .bar .foo.

And a > li#wag.pit (whose last compound selector is li#wag.pit) will be compared to div li#wag.pit and a > b > li + li#wag.pit, but not to li or li #wag, etc.

Selectors targeting pseudo-elements are not considered comparable to similar selectors without the pseudo-element, because they target other elements on the rendered page. For example, a::before {} will not be compared to a:hover {}, because a::before targets a pseudo-element whereas a:hover targets the actual <a>.

This rule only compares rules that are within the same media context. So a {} @media print { #baz a {} } is fine.

This rule resolves nested selectors before calculating the specificity of the selectors.

DOM Limitations

The linter can only check the CSS to check for specificity order. It does not have access to the HTML or DOM in order to interpret the use of the CSS.

This can lead to valid linting errors appearing to be invalid at first glance.

For example the following will cause an error:

.component1 a {}
.component1 a:hover {}
.component2 a {}

This is a correct error because the a:hover on line 2 has a higher specificity than the a on line 3.

This may lead to confusion because "the two selectors will never match the same a in the DOM". However, since the linter does not have access to the DOM it can not evaluate this, and therefore correctly reports the error about descending specificity.

It may be possible to restructure your CSS to remove the error, otherwise it is recommended that you disable the rule for that line and leave a comment saying why the error should be ignored. Note that disabling the rule will cause additional valid errors from being reported.

block-closing-brace-newline-after

Require a newline or disallow whitespace after the closing brace of blocks.

a { color: pink; }
a { color: red; }↑
/**              ↑
 * The newline after this brace */

This rule allows an end-of-line comment separated from the closing brace by spaces, as long as the comment contains no newlines. For example,

a {
  color: pink;
} /* end-of-line comment */

This rule allows a trailing semicolon after the closing brace of a block. For example,

:root {
  --toolbar-theme: {
    background-color: hsl(120, 70%, 95%);
  };
/* ↑
 * This semicolon */
}

The [fix option](../../../docs/user-guide/usage/options.md#fix) can automatically fix all of the problems reported by this rule.

block-closing-brace-space-before

Require a single space or disallow whitespace before the closing brace of blocks.

a { color: pink; }
/**              ↑
 * The space before this brace */

The [fix option](../../../docs/user-guide/usage/options.md#fix) can automatically fix all of the problems reported by this rule.

declaration-block-semicolon-space-after

Require a single space or disallow whitespace after the semicolons of declaration blocks.

a { color: pink; top: 0; }
/**            ↑
 * The space after this semicolon */

This rule ignores:

• semicolons that are preceded by Less mixins
• the last semicolon of declaration blocks

Use the block-closing-brace-*-before rules to control the whitespace between the last semicolon and the closing brace instead.

The [fix option](../../../docs/user-guide/usage/options.md#fix) can automatically fix all of the problems reported by this rule.