[wp-trac] [WordPress Trac] #36335: Next generation: core autoloader proposal

[WordPress Trac]

#36335: Next generation: core autoloader proposal
-----------------------------+------------------
 Reporter:  dnaber-de        |       Owner:
     Type:  feature request  |      Status:  new
 Priority:  normal           |   Milestone:  4.7
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  has-patch        |     Focuses:
-----------------------------+------------------

Comment (by wonderboymusic):

 Remaining steps:

 1) to avoid collision, I say we name it `wp-vendor` and leave it outside
 `wp-includes`

 2) Commit the `composer.lock` and `wp-vendor` files

 3) Do a patch that rips out every `require(_once)?` for every class that
 is in the classmap, and add the inclusion of the Autoloader to `wp-
 settings.php`

 4) Move the function files into `autoload.files` slowly, and remove their
 extraneous includes, running unit test after each file. We need to make
 sure that no file produces unexpected side effects. If so, we will move
 the side effects to `wp-settings.php`

 Can everyone please agree on `wp-vendor`? If not, why not? Also, any
 tweaks for `composer.json`, let's do those as step #0.

 The reason I am racing to get this in is to see what may or may not break.
 #early #yolo

 WordPress is going on a massive diet.

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