[wp-trac] [WordPress Trac] #21170: JavaScript actions and filters

WordPress Trac noreply at wordpress.org
Wed Sep 13 23:51:18 UTC 2017


#21170: JavaScript actions and filters
-----------------------------+------------------------------
 Reporter:  koopersmith      |       Owner:  adamsilverstein
     Type:  feature request  |      Status:  reopened
 Priority:  normal           |   Milestone:  4.9
Component:  General          |     Version:  3.4
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:  javascript
-----------------------------+------------------------------

Comment (by adamsilverstein):

 > We have been experimenting with decorators, exploring slot & fill
 patterns, and dabbled with middlewares. There are some great points in
 these to build from. We do need some more tangible examples to define and
 implement any solution. Gutenberg gives us a good place to try them.

 @matveb do you feel that decorators, slot and fill patterns or middleware
 would be applicable to extending our existing core JavaScript, especially
 our single page Backbone Apps?

 > I'd want to see something using a modern library (Be that React, Vue,
 Angular, Whatever) using this pattern before we add it as-is to WordPress,
 if it proves to be useful in that context then I'd be all for this, but
 only after a reasonably complex application had tried it.

 @dd32 I'm excited to see Gutenberg
 [https://github.com/WordPress/gutenberg/issues/2474#issuecomment-327875802
 exploring wp.hooks as a possible api for adding extensibility]. At the
 same time, I am trying to forward the ongoing effort  to make our existing
 JavaScript more accessible and extendable - especially our single page
 apps - the media modal, the media grid, the new theme browser, the
 installed theme browser, the customizer, the editor and the revisions
 screen (i may have missed some). `wp.hooks` seems like a great fit make
 these components more extendable, 'modern' JavaScript approaches may not
 be as good a fit.  How would you propose we work on making our existing
 JavaScript more extendable in core? Wait until the Gutenberg project
 decides how to approach extendability, then see if we can retroactively
 apply that approach to our legacy JavaScript?

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


More information about the wp-trac mailing list