[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:  defect (bug)      |      Status:  reopened
 Priority:  normal            |   Milestone:  7.0
Component:  AI                |     Version:  trunk
 Severity:  normal            |  Resolution:
 Keywords:                    |     Focuses:
------------------------------+-------------------------------
Changes (by jorbin):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 The [https://make.wordpress.org/core/2025/11/10/abilities-api-in-
 wordpress-6-9/#:~:text=Ability%20Naming%20Conventions dev note from when
 abilities was introduced] states that these are namesapaces that aim to
 prevent conflicts. This is inline with blocks and the rest API.
 Introducing a new way for slashes to be used introduces unnecessary
 differences between abilities and other apis in core.

 If we are looking for a way to give core provided abilities better
 prominence, than perhaps what should be explored is a `_built_in` flag
 similar to post types.


 [61602] should be reverted.

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