[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 dnaber-de):

 Heyo Giuseppe,

 thanks for your response.

 You're absolutely right, the core is at the moment not able to switch to a
 common autoloading system. I am aware of that. Moving the core to a one-
 class-per-file structure is worth another ticket, I think. (It is at least
 a sub-task of the big complex «autoloader». And by the way probably the
 most complicated part.)

 The first focus from my perspective is to provide a working example of a
 possible implementation that comply with these two points:

  * being a proof of concept. That means to show people that is it
 generally possible. Even more, having a existing example make it easier to
 understand and discuss the concept.
  * being flexible, so that it can be used in any way we want.

 I could also imagine a sequential introduction. In the first release the
 autoloader is introduced. In a next release everything in `wp-admin/` is
 moved to the autoloader and so on.

 Anyway, the major benefit of having an autoloader would be having a
 consistent way for plugin authors and later talking about
 dependency/package management. Because we're runing into a big issue with
 inconsistent packages, when plugin authors keep on using composer and ship
 their dependencies with their plugins. And they will.

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