[wp-trac] [WordPress Trac] #36335: Next generation: core autoloader proposal
WordPress Trac
noreply at wordpress.org
Thu Sep 1 20:22:33 UTC 2016
#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 MikeSchinkel):
Replying to [comment:152 TJNowell]:
> I would note that a Composer autoloader is not a full copy of
Composer...
Pulling back from the debate thanks to @chrisvanpatten and your comments,
it is clear I am not even clear what is being debated on this ticket. I
think the reason is because this ticket was inadvertently hijacked to go
in a different direction from the OP's intent.
Minimally I think if we are going to discuss an autoloader based on
Composer we should respect @dnaber-de and not hijack his ticket. Instead
we should discuss his proposal ''(which I think is mostly good)'' and give
it a thumbs up or a thumbs down.
If we instead want to advocate for a Composer autoloader it should be
written up in another ticket form and we can and should debate it there.
So rather than me answer your questions here '''I would suggest''' someone
who is a strong advocate of using a Composer autoloader '''create a clear
proposal on another ticket and link from here to that ticket''' and then I
can register my objections (or agreements) there.
> Mike, if you'd like to work on a generator proposal...
Frankly if we consider this ticket's original proposal it would be very
close to what I would propose so it would not make sense for me to split
discussion of improvements to @dnaber-de's proposal on to another ticket.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/36335#comment:154>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list