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

WordPress Trac noreply at wordpress.org
Thu Sep 14 00:36:03 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 dd32):

 > How would you propose we work on making our existing JavaScript more
 extendable in core?

 Honestly, I can't answer that right now. However a lot of the code in
 question has been operating in it's current state for quite some time,
 another few {insert time length here} isn't going to do a huge amount of
 harm in the long run. Many have some form of extensibility worked in
 through unexpected and sometimes convoluted methods that others have
 already been using.

 I'm more concerned with having building blocks for the future that feel
 native, rather than potentially forced to fit in. In other words, I'd
 rather attempt to retroactively apply whatever the ultimate solution here
 to legacy code, than for future code to build upon something that was
 designed for a different era of Javascript. If that means that some legacy
 code remains non-accessible/extendable even longer, I'm not too worried
 about that.

 Whether we like it or not, a lot of the existing Backbone-based interfaces
 are likely to change in the future as design/feel/JS code/etc is
 integrated into a cohesive platform that works the same, no matter which
 page you're looking at.
 Once upon a time it looked like all of WordPress would be built upon
 Backbone, today, finding someone who would choose Backbone over anything
 else is near impossible. I would not be surprised if all of the Backbone
 apps you listed were not rewritten (or being rewritten) using a react-like
 library within the next 3 years (to throw some form of timeline out there,
 that I'm fairly confident of).

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


More information about the wp-trac mailing list