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.
|
// Mixins should always be first in declarations |
|
'order/order': [ |
|
{ |
|
name: 'include', |
|
type: 'at-rule', |
|
}, |
|
'declarations', |
|
], |
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.
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
@includemixins 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.