[wp-trac] [WordPress Trac] #64596: Abilities API: Allow nested namespace ability names (2-4 segments)

[WordPress Trac]

#64596: Abilities API: Allow nested namespace ability names (2-4 segments)
--------------------------------------+-------------------------------
 Reporter:  jorgefilipecosta          |       Owner:  jorgefilipecosta
     Type:  enhancement               |      Status:  reopened
 Priority:  normal                    |   Milestone:  7.0
Component:  AI                        |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+-------------------------------

Comment (by jorbin):

 > That's why we intentionally designed what we merged into 6.9 around
 being about to make this decision in 7.0 in the most graceful possible way

 Where was this discussed? It wasn't on #64098 which is where the decision
 to merge the abilities API was made.

 Stepping back, the arguments I see in favor of nesting are:

 > organizing abilities into logical resource groups

 As pointed out, ability catagories are the canonical way to group
 abilities. Expecting people to run a substring search on all of the
 abilities isn't creating logical groups, it's creating unnecessary
 complication.

 > We plan to use this new type of naming for post abilities.

 Assuming this is referring to #64455, that ticket is no longer in the 7.0
 milestone.

 As much as it strains me to quote @nacin, he rightfuly credited
 WordPress's success to being "...because the project maintainers deal with
 all the pain — technical debt, undoing breakage in upstream libraries,
 working on as many server (mis)configurations as possible — its users
 don’t have to."[1] Forcing version detection onto each plugin is forcing
 pain on to them. And for what? So there can be a second way to create
 groupings? In order for the abilities API to do namespaces differently
 than every other part of core that does namespaces?


 1)
 https://web.archive.org/web/20140417182355/http://opensourcebridge.org/proposals/1413

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64596#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform