[wp-trac] [WordPress Trac] #36335: Next generation: core autoloader proposal
WordPress Trac
noreply at wordpress.org
Sun Sep 4 08:59:55 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:162 tfrommen]:
> The "proposal" is presented in [https://www.alainschlesser.com/adding-
central-autoloader-wordpress/ this post].
Thanks. That was very helpful.
However, the proposal did not summarize so I'm still a bit unclear with
what is being proposed. Let me summarize to see if I can get it right:
1. Add `composer.json` to WordPress ''(which BTW I am definitely in favor
of)''
2. Change `wp-config.php` to load a Composer autoloader.
3. Generate a PHP52 compatible autoloader using `xrstf/composer-php52`
4. Have Composer generate a classmap for `wp-includes` directory
5. Fix anything in `wp-includes` that is not 1 file=1 class.
6. Include the generated classmap and autoloader with WordPress core.
7. Once we get beyond PHP52, bundle Composer into WordPress core.
Did I correctly summarize the proposal that is currently being debated?
If not, what did I get wrong?
--
Ticket URL: <https://core.trac.wordpress.org/ticket/36335#comment:169>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list