[wp-trac] [WordPress Trac] #47678: Modernize/simplify current_user_can()

[WordPress Trac]

#47678: Modernize/simplify current_user_can()
-------------------------------------+-------------------------------------
 Reporter:  jrf                      |       Owner:  pento
     Type:  enhancement              |      Status:  assigned
 Priority:  normal                   |   Milestone:  5.3
Component:  Role/Capability          |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch has-unit-      |     Focuses:  performance, coding-
  tests commit needs-dev-note        |  standards
-------------------------------------+-------------------------------------

Comment (by jrf):

 **Status summary:**

 Ok, so there are still three patches to be (re-)committed before this
 ticket can be closed:
 * `47678-do_action-spread-operator-v2.patch`
 * `47678-Walker-walk.patch`
 * `47678-Walker-paged_walk.patch`

 A [https://gist.github.com/jrfnl/23fa057e5a951ab8b6bf8709e5e5b281 dev-note
 to accompany the changes has been prepared].

 Before publishing the dev-note, I'd like to get clarification on whether
 the `Walker` class patches will or will not go into WP 5.3 as they should
 be included in the dev-note if they go in.

 And if they don't go in, WP 5.4 (or whatever future version) would again
 need a separate dev-note.

 What will all the research done for this and spelled out above in comments
 23 up to 29, the change can be estimated to impact ~0.05% of plugins and
 themes.

 Aside from that, the way the change has been made, those can be fixed in a
 BC-compatible way, as in: the affected plugins/themes don't need to drop
 support for older WP versions to be compatible with WP 5.3. They only need
 to drop support for PHP < 5.6.
 See the dev-note for more details.

 @pento What say you ?

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