Currently (as of v0.17.9) rule order of themes (Apex & MediaWiki) elements and widgets' Less files is historically grown and/or chaotic.
Example of MediaWiki theme's widgets.less rule order:
- .theme-oo-ui-widget () {}
- .theme-oo-ui-outlineControlsWidget () {}
- .theme-oo-ui-toggleWidget () {}
- .theme-oo-ui-buttonGroupWidget () {}
- .theme-oo-ui-buttonWidget () {}
- .theme-oo-ui-actionWidget () {}
- .theme-oo-ui-popupButtonWidget () {}
and so forth.
Functionally, this has no negative impact, but from a contributors POV this might be judged as unprofessional.
There are three possible options here for me right now:
- leave the status quo – update after patch: Git seems to not be able connect the moved blocks, so we git blame history is at risk :/
- sort purely alphabetically, with probably the exception of having a more basic one buttonWidget come before buttonGroupWidget, which builds on top
- sort alphabetically, but also sub-group similar one likes .theme-oo-ui-inputWidget and .theme-oo-ui-textInputWidget
Before | After |
---|---|