[wp-trac] [WordPress Trac] #36335: Next generation: core autoloader proposal
WordPress Trac
noreply at wordpress.org
Fri Aug 26 21:58:06 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 jorbin):
Some additional questions:
How do we ensure composer.json's autoload.files property stays up to
date? Is this something that needs to updated manually? Should there be
a grunt pre commit hook to help with this? Something else? Are there any
regular composer file
Do we have anything to worry about if plugins are using composer or the
5.2 autoloader? Is there a string we can grep the plugin repo for so we
can alert any plugin authors?
I added the `composer.lock` file in my patch. Was there a specific reason
for not including it before?
Let's also do a review of the composer.json file to ensure it has only the
things we want. I haven't done it yet, but
[https://getcomposer.org/doc/04-schema.md found the schema] for
composer.json
Tasks that are still needed:
- Update .travis.yml to include 5.2 with SPL disabled.
- Draft a post for make/core with what developers need to do to test and
how they can update their code.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/36335#comment:75>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list