WordPress.org

Making WordPress.org

Changes between Initial Version and Version 1 of Ticket #3876, comment 27


Ignore:
Timestamp:
01/17/2019 09:59:21 AM (5 months ago)
Author:
timwhitlock
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #3876, comment 27

    initial v1  
    77The new system creates complexities which may be ok for Core development, but many plugin and theme developers looking to use the new system will struggle to prepare their sources. I know this, because I'm already beginning to hear from them.
    88
    9 Ensuring file references match production code will cause some people problems. (e.g. `src/library/component.js` won't match `dist/prod.js`). I know this has been considered because WP handles `.min.js`, but there are many common practices that won't produce that result. Using command line tools to generate PHP files with `/* references: */` seems like unnecessary wrangling for simple cases.
     9Ensuring file references match production code will cause some people problems. (e.g. `src/library/component.js` won't match `dist/prod.js`). I know this has been considered because WP handles `.min.js`, but there are many common practices that won't produce that result, and using command line tools to generate PHP files with `/* references: */` seems like unnecessary wrangling for simple cases.
    1010
    1111I agree that following WordPress standards is a fair requirement for being GlotPress-compatible, and I support that. However, in this case I feel like the requirements are unnecessarily restrictive and error-prone.