[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:                   |     Focuses:
-----------------------------+-----------------------------

Comment (by greg1anderson):

 Replying to [comment:17 dnaber-de]:
 > > having a single autoloader for the entire application
 > That's what this ticket is all about. :)

 Yes, absolutely. What I really intended to say here was that there should
 be a single composer-generated autoloader for the entire application. When
 you start calling `spl_autoload_register` directly, though, and you
 provide a way for plugins to provide classes of their own, you quickly
 move into a space where plugin authors need or desire to introduce
 dependencies of their own. During development, it is common to overlook
 the problems that can be caused when plugins provide dependencies that are
 not coordinated by the top-level application. Such solutions will often
 appear to work well for quite a long time, because problems are not
 evident until subtle differences in dependencies cause a conflict.

 @schlessera already made the most important points in 14. The best way
 forward is to bring in all dependencies via `composer require` from the
 project root.

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