-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
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
Shift lower specificity classes first, then higher specificity classes (when using namespace) #853
Comments
It may be possible to do so, but would you be able to add a https://stylelint.io/user-guide/ignore-code/#files-entirely If we don't need to add this feature, I'd prefer not to. |
I can ignore the generated Atomic CSS file, but don't want to really because Atomizer generates values for incorrect units as well. So Stylelint is helping me to catch these errors. |
Hi
I'm using this stylelint plugin https://stylelint.io/user-guide/rules/no-descending-specificity/, which disallow selectors of lower specificity from coming after overriding selectors of higher specificity.
I'm getting this error in my CSS file, which is generated via Atomizer.
Feature Request in Atomizer tool
Is it possible to shift lower specificity classes first, and then comes higher specificity classes (if using namespace) ?
Expected Output:
I'm using Atomizer version 3.28.0
The text was updated successfully, but these errors were encountered: