Add support for enabling a rule with stylelint-command comments

What is the problem you’re trying to solve?

Enabling a rule (with options) using stylelint-commands.

What solution would you like to see?

Being possible to write e.g.

/* stylelint declaration-no-important: [ true, { severity: 'warning' } ] */

to enable declaration-no-important with warning severity for a single file.

[jeddy3]

This feature SGTM. It’s likely related to https://github.com/stylelint/stylelint/issues/2643 as files are linted first and then errors within disable ranges are removed. Feel free to investigate how the stylelint-commands code can be rearchitected to facilitate a new /* stylelint .. */ command comment, as it’ll involve gathering the stylelint-commands before any linting happens so that the final configuration is known beforehand.

Now is a good time to look into this as the internals have been improved as we move towards releasing 14.0.0 (see https://github.com/stylelint/stylelint/pull/5542 & https://github.com/stylelint/stylelint/pull/5521, in particular).

These command comments should take the highest precedence, over overrides and (the yet to be added) --rules flag.

I’ve labelled the issue as ready to implement. Please consider contributing if you have time.

[AndreasNasman]

Not sure what you mean @stof. You can enable/disable/customize ESLint rules through comments anywhere in a file. The rules also don’t have to be configured in eslintrc beforehand, so they can be ‘enabled from scratch’ so to say. This issue is not about enabling unknown rules, it’s about improving the Stylelint comments to allow for customizing of available rules. 🙂