[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:  Future Release
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  2nd-opinion      |     Focuses:
-----------------------------+-----------------------------

Comment (by boonebgorges):

 A Composer-generated classmap seems like the right way forward here. I
 don't see why we should reinvent the wheel, even if it only takes 47 lines
 to do it.

 I have some implementation questions about how a Composer classmap would
 work alongside the WP codebase, which could probably be answered with a
 patch from someone with more Composer-fu than I've got. Putting a
 composer.json in the root of the repo checkout and running `composer dump-
 autoload` puts the autoloader into `/vendor`. What's the best practice for
 moving it into `ABSPATH`? Should we have a (Grunt?) wrapper that runs
 `dump-autoload` and then moves `vendor` into `src`, intended to be run
 pre-commit?

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