We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What is the problem you're trying to solve?
We are working on a global CS tool including stylelint for both .css and .scss file (with the scss plugin).
.css
.scss
Some CSS rules does not have to apply on .scss file. Please see our issue for details: https://gitlab.com/nexylan/pretty/issues/23
The only workaround I have now is to completely disable the function-name-case rule, even for .css files.
function-name-case
What solution would you like to see?
Have the possibility to define a overrides section on the configuration file.
overrides
The way eslint does it seem pretty good: https://eslint.org/docs/user-guide/configuring#disabling-rules-only-for-a-group-of-files
We may do something like this:
plugins: - stylelint-scss extends: - stylelint-config-standard - stylelint-config-recommended-scss - stylelint-config-prettier overrides: files: - '*.scss' rules: function-name-case: null
Or include the plugin on overrides:
extends: - stylelint-config-standard - stylelint-config-prettier overrides: files: - '*.scss' plugins: - stylelint-scss extends: - stylelint-config-recommended-scss
As overrides would be able to handle any config as the root one, you have a lot of possibilities.
Regards
The text was updated successfully, but these errors were encountered:
Duplicates #3128
Sorry, something went wrong.
Oh didn't see that one, thanks and sorry for the duplicate!
No branches or pull requests
We are working on a global CS tool including stylelint for both
.css
and.scss
file (with the scss plugin).Some CSS rules does not have to apply on
.scss
file. Please see our issue for details: https://gitlab.com/nexylan/pretty/issues/23The only workaround I have now is to completely disable the
function-name-case
rule, even for.css
files.Have the possibility to define a
overrides
section on the configuration file.The way eslint does it seem pretty good: https://eslint.org/docs/user-guide/configuring#disabling-rules-only-for-a-group-of-files
We may do something like this:
Or include the plugin on
overrides
:As
overrides
would be able to handle any config as the root one, you have a lot of possibilities.Regards
The text was updated successfully, but these errors were encountered: