[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 boonebgorges):

 Replying to [comment:164 swissspidy]:
 > Replying to [comment:163 schlessera]:
 > > One more though on the general direction of this ticket:
 > >
 > > My preference would be to only consider Composer as built-time tool
 for now to build a 5.2-compatible class map that WordPress Core can use.
 Then use this to modify Core so that it can make better use of the
 autoloader. I expect his to have a positive impact (directly and
 indirectly) on the code quality and architecture of Core.
 > >
 > > Considering writing an API to provide a class autoloader to plugins &
 themes is too early right now, and not all of the preconditions for
 properly designing something like this are met yet.
 >
 > I think this sums it up quite nicely.

 Agreed. To reiterate: the only use of Composer being suggested here is to
 generate a classmap at build time. The only people who will ever have to
 worry about using Composer, on this proposal, are committers, and core
 contributors whose patches change the classmap (by
 adding/removing/renaming classes).

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