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
step Stylelint configuration and run Styelint in CLI.
json { "extends": ["stylelint-config-standard"], "plugins": ["stylelint-order"], "rules": { "custom-property-empty-line-before": [ "always", { "except": ["after-comment", "after-custom-property", "first-nested"], "ignore": ["after-comment", "inside-single-line-block"] } ], }, "overrides": [ { "files": ["**/*.vue"], "customSyntax": "postcss-html", "extends": ["stylelint-config-recommended-vue", "stylelint-config-standard-scss", "stylelint-config-recommended-vue/scss"] } ] }
CLI with `stylelint src/views/SamplePage.vue --config .stylelintrc'
14.6.1
<div class="home-container" style="--text-color: #1352ba;"> Sample </div>
<div class="home-container" style=" --text-color: #1352ba;"> Sample </div>
No response
The text was updated successfully, but these errors were encountered:
@MarkSky Thanks for the report and for using the template.
The stylistic rules are frozen. We recommend enforcing whitespace conventions using a pretty printer like Prettier alongside Stylelint.
Alternatively, you can:
style="--text-color: #1352ba;">
custom-property-empty-line-before
Sorry, something went wrong.
I understand. Thank you. Will these rules remove from standard rules in the future version?
No branches or pull requests
What steps are needed to reproduce the bug?
step Stylelint configuration and run Styelint in CLI.
What Stylelint configuration is needed to reproduce the bug?
How did you run Stylelint?
CLI with `stylelint src/views/SamplePage.vue --config .stylelintrc'
Which version of Stylelint are you using?
14.6.1
What did you expect to happen?
What actually happened?
Does the bug relate to non-standard syntax?
No response
Proposal to fix the bug
No response
The text was updated successfully, but these errors were encountered: