[wp-trac] [WordPress Trac] #29546: grunt uglify for plugins and plugin developers

WordPress Trac noreply at wordpress.org
Tue Oct 21 06:59:19 UTC 2014


#29546: grunt uglify for plugins and plugin developers
------------------------------+--------------------
 Reporter:  MattyRob          |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  4.1
Component:  Build/Test Tools  |     Version:  trunk
 Severity:  trivial           |  Resolution:
 Keywords:  has-patch         |     Focuses:
------------------------------+--------------------

Comment (by dd32):

 > Plugin and theme authors should be using either core. SVN/Git repo or
 use a custom wp-content folder alongside the /build folder of the develop.
 SVN/Git repo.

 There's nothing wrong with using `src` for plugin development. Sure, they
 won't have RTL or minified styles, and won't have colour schemes, but that
 shouldn't impact upon most plugin development.
 For testing, there's no question about it, if they're using the develop
 repo, they should then run `grunt build` to copy wp & the plugin to the
 `build` directory, where they can test those aspects of the plugin. That's
 an expected behaviour if they're using the develop repo.

 That being said, I don't think core's grunt utils need to support plugin
 development, and that instead, we should maybe make available an example
 grunt-for-plugins `Gruntfile.js` for plugins usage, it'd encourage more
 plugin authors to take that route IMHO, customizing the Gruntfile as
 required for their plugin.

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


More information about the wp-trac mailing list