With 📌 Integration with Gitlab CI Fixed in place, we can start checking for Stylelint. There is a report now for the issues we can fix.
css/global.css
1:57 ✖ Expected double colon pseudo-element notation selector-pseudo-element-colon-notation
5:52 ✖ Expected double colon pseudo-element notation selector-pseudo-element-colon-notation
8:54 ✖ Expected double colon pseudo-element notation selector-pseudo-element-colon-notation
12:52 ✖ Expected double colon pseudo-element notation selector-pseudo-element-colon-notation
20:5 ✖ Expected "cursor" to come before "font-weight" order/properties-order
28:119 ✖ Expected double colon pseudo-element notation selector-pseudo-element-colon-notation
33:114 ✖ Expected double colon pseudo-element notation selector-pseudo-element-colon-notation
38:116 ✖ Expected double colon pseudo-element notation selector-pseudo-element-colon-notation
43:114 ✖ Expected double colon pseudo-element notation selector-pseudo-element-colon-notation
81:5 ✖ Expected "color" to come before "font-weight" order/properties-order
81:38 ✖ Expected "--colorGinText" to match pattern "^[a-z][-_a-z0-9IE]*$" custom-property-pattern
11 problems (11 errors, 0 warnings)
1 source checked
/builds/project/admin_toolbar_content/web/modules/custom/admin_toolbar_content/css/global.css
11 errors found
selector-pseudo-element-colon-notation: 8 (maybe fixable)
order/properties-order: 2
custom-property-pattern: 1
Run stylelint
Fixed
2.0
Code
Issue #3421311 by tim-diels: Fix issues reported by Stylelint