Do not run scss/* rules on non-SCSS files

[unikitty37]

What is the problem you're trying to solve?

I use SCSS, and the stylelint-scss rules at https://github.com/kristerkari/stylelint-scss. However, there are some plain CSS files in the project as well, and some stylelint-scss rules do not work well when run against plain CSS.

(Example: setting scss/comment-no-loud to true means no comments can be used in .css files, as it disallows /* … */ and only permits // — but this is not valid in plain CSS.

What solution would you like to see?

An ability to prevent SCSS-specific rules from running on non-SCSS files.

Ideally, stylelint-scss would be able to declare that its rules should only run against files detected to be SCSS (whether by checking the extension or some other means).

A second-best option would be allow stylelint-disable to accept wildcards — placing stylelint-disable scss/* at the start of every .css file would be annoying, but a reasonable workaround. Listing every rule starting scss/ individually would not be reasonable 😁 — nor would leaving the offending rules disabled by default and manually enabling them at the top of .scss files

I originally filed this at stylelint-scss/stylelint-scss#352, but was told it needed to be addressed in stylelint itself.

[vankop]

As a workaround I can suggest run stylelint twice with different configs. I don't know good solution for IDE stylelint support.

[hudochenkov]

Some of stylelint-scss could be applied to non-SCSS syntaxes. E. g. if someone uses $variables in their style sheet with PostCSS plugin. Then they could use dollar-variables rules from stylelint-scss, while not using SCSS itself.

We have two solutions:

1. overrides object in configuration Add overrides property to configuration object #3128 But it's not implemented yet :(
2. Use separate configs and run stylelint twice. You can extends you main config in config for CSS and run stylelint for CSS as: stylelint "**/*.css" --config my-stylelint-css-config.json.

[jeddy3]

overrides object in configuration #3128 But it's not implemented yet :(

Yep, I think this is covered by the overrides feature that is present in other linters. @unikitty37 That issue is labeled as "help wanted", so feel free to contribute it if you've time.

---

Closing in favour of #3128

[unikitty37]

Unfortunately, the workaround is no workaround for me, as I need IDE support :(

I wish I had time — and enough Node knowledge — to help on #3128…