Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Add CSS linter to gulp tasks #797
It's possible to write malformed CSS that can be properly interpreted by most browsers, but will cause problems when passed through the minification process. As a result, you can end up with styling that worked fine in development, but fails in production.
Adding a CSS linter to the build pipeline would ensure that problems like this are flagged, rather than silently breaking styling when you deploy malformed CSS.
Having some service to lint this project as a whole would be a good idea however the benefits would be limited to us.
I've been thinking about this for some time now, and I think the best solution here would be allowing custom scripts in each sprinkle. Work done for 4.2 (common frontend dependencies location, much like how we resolve backend dependencies via composer to a common location) opens up
In terms of linting CSS the thought process is that we have a default linter that can be run, but allow individual to override this with their own.
I'd like to see this expanded with a few build hooks to better facilitate more complex build process in time, that however will be much more complex as