[wp-trac] [WordPress Trac] #36335: Next generation: core autoloader proposal
WordPress Trac
noreply at wordpress.org
Sat Aug 27 01:40:08 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 GaryJ):
Replying to [comment:80 wonderboymusic]:
> 1) to avoid collision, I say we name it `wp-vendor` and leave it outside
`wp-includes`
As I was reading the last few comments, `wp-vendor` at the top level is
what sprung to mind for me too, so I'm +1 to this if top-level `vendor` is
a no-go.
Any reason for selecting `1.*` as the version for `xrstf/composer-php52`,
instead of `^1.0`? Composer
[https://getcomposer.org/doc/articles/versions.md#caret lists] the latter
as being "the recommended operator for maximum interoperability when
writing library code."
--
Ticket URL: <https://core.trac.wordpress.org/ticket/36335#comment:82>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list