[wp-trac] [WordPress Trac] #59669: Block: Give `traverse_and_serialize_block(s)`' post-callback access to block instance

WordPress Trac noreply at wordpress.org
Wed Nov 1 12:45:40 UTC 2023


#59669: Block: Give `traverse_and_serialize_block(s)`' post-callback access to
block instance
-------------------------------------------------+-------------------------
 Reporter:  Bernhard Reiter                      |       Owner:  Bernhard
                                                 |  Reiter
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  6.4
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests commit      |     Focuses:
  dev-reviewed                                   |
-------------------------------------------------+-------------------------

Comment (by azaozz):

 Just curious, why callbacks (as function params) and not filters? The
 (basic) difference between callbacks as params and filters is that with
 filters many plugins can apply callbacks at the same time, i.e. work in
 sync. With separate callbacks all plugins will have to rerun the same
 functions again and again.

 Looking ast gthe code here, these callbacks seem like an anti-pattern in
 WP?

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


More information about the wp-trac mailing list