[wp-trac] [WordPress Trac] #64596: Allow ability names to contain multiple slug fragments (2-4 segments)

[WordPress Trac]

#64596: Allow ability names to contain multiple slug fragments (2-4 segments)
--------------------------------------+-------------------------
 Reporter:  jorgefilipecosta          |       Owner:  justlevine
     Type:  enhancement               |      Status:  assigned
 Priority:  normal                    |   Milestone:  7.1
Component:  Abilities API             |     Version:  6.9
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+-------------------------

Comment (by gziolo):

 Related discussion is happening in other tickets as well, especially
 #64345 around versioning, so I think it is worth keeping the concerns
 separate here. For this ticket, I’m skeptical about allowing additional
 slash-delimited levels in ability names. I understand the appeal for
 readability and grouping, but I’m concerned that the ability name would
 start carrying too many roles: ownership namespace, hierarchy, filtering,
 and routing-like semantics.

 This also gets awkward once abilities are exposed through REST. For
 example: `/wp-json/wp-abilities/v1/abilities/math/v5/calculator`. Even if
 technically valid, that reads like overlapping REST/API versioning and
 nested routing, when the ability name should ideally remain a simple,
 stable identifier.

 I would prefer to keep ability names limited to the current namespace/name
 shape and rely on categories, metadata, schema, and discovery filters for
 grouping and querying. Unless there is a strong use case that cannot be
 handled by the existing structured mechanisms.

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