-
Notifications
You must be signed in to change notification settings - Fork 4
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
Potential issue with sorting #37
Comments
Maybe a more suitable rule could be
This ignores at-rules and at-variables - allowing them to be in any order but will make sure there is some predictable order in the blocks. https://github.com/hudochenkov/stylelint-order/blob/master/rules/order/README.md Another idea could be to make |
Indeed! This is the configuration from Torchbox for reference: 'order/order': [
'dollar-variables',
'custom-properties',
// @-rules that have no nesting.
{ type: 'at-rule', hasBlock: false },
'declarations',
], |
Kindly assign this to me .I want to work on this issue |
This might not be a good contribution issue @anshikavashistha but thanks for your interest. I'm still waiting on feedback for a related PR I to Wagtail that will impact the direction on this issue. Additionally, it's possible these rules will not work as is for Wagtail core and more investigation will be needed. |
okay sure @lb- |
- Do not be so strict with rule usage, it may make sense for blocks (e.g. @media) to be after other content - Closes wagtail#37
- Do not be so strict with rule usage, it may make sense for blocks (e.g. @media) to be after other content - Closes wagtail#37
PR up #39 |
- Do not be so strict with rule usage, it may make sense for blocks (e.g. @media) to be after other content - Closes wagtail#37
I just started to resolve wagtail/wagtail#10719 and have realised that our sorting rules could be causing some issues.
When I run the stylelint formatter / fixer on the Wagtail codebase I see that it's moving all our
@include
mixins to the top of the selector block.stylelint-config-wagtail/index.js
Lines 36 to 43 in b5986bb
From my understanding, this will actually cause a few problems where the styles will not be overridden at breakpoints.
Context of this change.
I know I merged this in but just wondering if there are some nuances for how mixins can be used that we should be allowing.
The text was updated successfully, but these errors were encountered: