WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #21170, comment 151


Ignore:
Timestamp:
09/13/17 15:29:21 (2 months ago)
Author:
adamsilverstein
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #21170, comment 151

    initial v1  
    33> Unfortunately, this was committed with a blocker not being addressed. 
    44 
    5 //Your blocker seems contrived//: we can't add a library to core until it is already used?  Just last week, our project leader @matt was telling us to [https://wordpress.slack.com/archives/C02RQBWTW/p1504729788000192 'more iteration happening in trunk']. Having this in trunk means we can build off it, using it in core itself and we have plans to do just that. 
     5//Your blocker seems contrived//: we can't add a library to core until it is already used?  Just last week, our project leader @matt was telling us to have [https://wordpress.slack.com/archives/C02RQBWTW/p1504729788000192 'more iteration happening in trunk']. Having this in trunk means we can build off it, using it in core itself and we have plans to do just that. 
    66 
    77> Even not considering modern practices, wp.hooks has no usage in Core, some parts of Core's legacy JS should be making use of it when it's committed.