[wp-trac] [WordPress Trac] #29792: Grunt: Add a precommit task to check for CSS syntax errors

[WordPress Trac]

#29792: Grunt: Add a precommit task to check for CSS syntax errors
------------------------------+-----------------
 Reporter:  helen             |      Owner:
     Type:  enhancement       |     Status:  new
 Priority:  normal            |  Milestone:  4.1
Component:  Build/Test Tools  |    Version:
 Severity:  normal            |   Keywords:
  Focuses:                    |
------------------------------+-----------------
 We need to do a better job of catching sad syntax errors and problems in
 our CSS before commit - things like parse errors, empty rules, units on
 zero values, and possibly duplicate properties (when alone, not as a part
 of a group). There may also be a thing or two that we could enforce per
 our own standards, such as requiring a comment to follow any declaration
 with `!important`.

 CSSLint seems to do most of these, provided we turn off the majority of
 its checks. Many of those checks (vendor prefixes, selector specificity,
 etc.) either are not relevant to our set up (due to Autoprefixer, for
 example) or are just not feasible given our current CSS and possibly not
 desirable for this project.

 Interested to know if there are any other tools out there that perhaps fit
 the job better, and defining the parameters of what we would like to
 check.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/29792>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform