[wp-trac] [WordPress Trac] #64098: Introduce Abilities API

[WordPress Trac]

#64098: Introduce Abilities API
--------------------------------------------------+---------------------
 Reporter:  gziolo                                |       Owner:  (none)
     Type:  feature request                       |      Status:  new
 Priority:  normal                                |   Milestone:  6.9
Component:  General                               |     Version:  trunk
 Severity:  normal                                |  Resolution:
 Keywords:  has-patch 2nd-opinion has-unit-tests  |     Focuses:
--------------------------------------------------+---------------------

Comment (by jorbin):

 I don't want to distract from the work happening on the pull request, so
 I'm raising this here so that this risk can be considered. I'm a bit
 concerned about adding a new API in 6.9 that core won't be using right
 away. This isn't to say it's not well-designed or well coded, but it's not
 really been through the paces. Where are the example abilities for
 extenders to learn from since they won't find them in core?

 The [https://github.com/search?q=wordpress%2Fabilities-
 api+language%3AJSON+composer.json&type=code public uses I can find are
 using a fairly old version] which makes me wonder how battle tested this
 code is. Parts of it are very new with [https://github.com/WordPress
 /abilities-api/graphs/code-frequency over 5k new lines of code in the last
 week].

 Further, what is gained by shipping this in core for 6.9 without any
 abilities for people to take advantage of vs shipping this as a plugin
 earlier and then merging at a later time? Once it ships, it's a lot harder
 to change things.

 Some of the things that I think could make good abilities for a v1
 implementation in core are many of the uses of admin-ajax in core right
 now.

 I wouldn't say that I'm -1 on merging, but I am somewhere between -0.25
 and -0.5 for these reasons. Essentially, how well do we know if this API,
 in this design format, is going to solve the needs of people if we don't
 yet know if it's going to solve the needs of Core?

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