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

WordPress Trac noreply at wordpress.org
Mon Oct 6 18:01:51 UTC 2014


#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            |  Resolution:
 Keywords:  has-patch         |     Focuses:
------------------------------+------------------

Comment (by jorbin):

 Replying to [comment:11 nacin]:
 >
 > With my patch applied to parserlib, this results in:
 >  * errors for unknown moz-document and ms-keyframes
 >  * no other errors
 >  * 65 warnings
 >
 > The warnings all seem like good things to fix:
 >  * non-adjacent duplicate properties (5)
 >  * unknown property values (3)
 >  * no fallback colors for RGBA usage (18)
 >  * one vendor-prefixed property without the standard property
 >  * one verbose property usage when shorthand will do (1)
 >  * zero units (17)
 >  * some display property grouping warnings (19)
 >  * one unqualified attribute (this one may be a bug)

 That seems less like syntax checking to me and more like stylistic
 checking.  Much like we use jsvalidate and jshint separately, I think this
 is two different separate tasks.

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


More information about the wp-trac mailing list