[wp-meta] [Making WordPress.org] #3692: Add CamelCase support from plugin names as per PSR-4 Autoloaders standard

[Making WordPress.org]

#3692: Add CamelCase support from plugin names as per PSR-4 Autoloaders standard
------------------------------+-----------------------
 Reporter:  KestutisIT        |       Owner:  (none)
     Type:  enhancement       |      Status:  reopened
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------

Comment (by KestutisIT):

 Replying to [comment:8 Otto42]:
 > You're misunderstanding. The WordPress code sends the folder name of the
 plugin, and we match it against the slug. That's how the update API works.
 >
 > So, before we even entertain the notion of allowing the folder name to
 not be the same as the slug of the plugin, then the WordPress core needs
 to have that concept built into it. It currently does not.
 >
 > So, this type of ticket is dependent upon the core code itself changing
 what it sends for update checks. It's not something we can just shove into
 the meta code, the WordPress core itself must act differently, and that
 would be something that belongs in core.trac.
 So let's the do this - I will create this ticket on track first with your
 notes added. Then it will go over the core.trac, get's into the core
 first, and then this ticket will be a next thing to proceed. So it still
 has not to be removed, just should not have the exact version yet, as we
 need to make a patch first for the core. And I the core I will also need a
 comment from you to list EXACT files where it (the update code for the
 slug check where I can add a check for "Namespace" meta header as and
 additional check option not just the "Text Domain" meta header, as what I
 understand this is from where you take the 'slug' value, right?). If you
 can, please write these related files and code lines like DION (@dd32) did
 with this plugin directory file, so that my ticket on core.track would be
 more exact and specific, and that I could propose a patch to save teams
 time on code writing. Thanks. I will also ask them Matt's and team lead's
 input there on that ticket in core.track.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/3692#comment:9>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org