[wp-trac] [WordPress Trac] #64596: Abilities API: Allow nested namespace ability names (2-4 segments)
WordPress Trac
noreply at wordpress.org
Thu Feb 12 14:47:17 UTC 2026
#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:
------------------------------+-------------------------------
Comment (by jorgefilipecosta):
Thanks so much @justlevine for the detailed and thoughtful response,
really appreciate you taking the time to lay all of that out, especially
from mobile! And thank you @jorbin for raising the consistency concern and
reopening the discussion, it's an important point.
I'll revert [61602] before beta1 so we don't have this landing under time
pressure.
I also want to walk back my comment #5 a bit, I didn't mean to jump ahead
and suggest we should lock in flat single-namespace names like core/get-
post right away either. @justlevine is right that we should have a real
conversation about what good naming looks like holistically before
committing to any pattern in core.
I think @justlevine raised some really compelling examples of existing
WordPress APIs that already use nested slug fragments (hierarchical post
types, REST subroutes like revisions, the Rewrite API, hooks, etc.), and
those are worth weighing alongside @jorbin's consistency concerns. Both
perspectives have a lot of merit here.
I love the idea of @justlevine and @jorbin syncing up to share context on
the prior discussions, and would love to participate. I think that could
save us a lot of back-and-forth and help us land on something we're all
happy with.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/64596#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list