[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:  assigned
 Priority:  normal            |   Milestone:  7.0
Component:  AI                |     Version:  trunk
 Severity:  normal            |  Resolution:
 Keywords:                    |     Focuses:
------------------------------+-------------------------------

Comment (by jorgefilipecosta):

 Replying to [comment:1 jorbin]:
 > > This is too restrictive for organizing abilities into logical resource
 groups.
 >
 > Isn't organizing abilities into groups why Ability Categories exist?

 Categories offer some layer of organization, discoverability, but we may
 still benefit from nesting. For example all these abilities may be on
 orders category:

 {{{
 my-plugin/orders/find
 my-plugin/orders/update
 my-plugin/orders/external/find
 }}}

 But nesting on `/external/` for orders coming from 3rd party marketplaces
 and that have a different retrieval mechanism may still be useful.

 In our case in core we will have a general category for post management
 across post types. To categorize all post management abilities as
 something similar but then we can have nesting to different post types
 something similar to:

 {{{
 core/posts/create
 core/pages/create
 }}}

 It is not a requirement to use multiple nesting levels but this change
 opens the door to its usage when it makes sense.

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