[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:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+-------------------------------

Comment (by jorbin):

 Thanks @jorgefilipecosta and @justlevine. Reverting still seems like the
 best choice. `svn merge -c -61602 '^/trunk' .` seems to work cleanly and
 i've just put https://github.com/WordPress/wordpress-develop/pull/10929 up
 to test and make sure there aren't any knock on affects.

 > I would strongly recommend against rushing to ship the functionality as
 a single-namespace into core without a real conversation about what good
 usage/holistic API looks like

 I worry that ship sailed since a single namespace is what shipped in 6.9.
 I completely agree that taking the time to get API design right is
 important since once something ships, it should stay supported in that
 form for a very long run. This is how we get and maintain user trust.

 > @jorbin Can you clarify your argument here and perhaps your broader
 concern with slug fragments (consumption, docs, dx, aesthetics, something
 else?)

 I think one of the reasons WordPress Core has gained the trust of its
 developer community is the ease of moving between different APIs. The fact
 that meta behaves the same regardless if it is for a comment, post, or
 user. The way `register_rest_route` and `` both should be run on specific
 actions. This consistency helps keep people in System 1 thinking which is
 much more productive.

 While WordPress's sustained position often gives a lot of credit to
 backwards compatibility, the forwards compatibility is also important.
 Knowing that an ability registered for 7.0 should work in 6.9 for anyone
 who hasn't upgraded helps with the adoption of features. While more and
 more sites upgrade quickly each release, there are always more risk-
 adverse people who wait for a x.y.1 or try to stay one major behind.

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