[wp-trac] [WordPress Trac] #59131: Introduce filters to modify/inspect the blocks returned by `do_blocks()`

[WordPress Trac]

#59131: Introduce filters to modify/inspect the blocks returned by `do_blocks()`
--------------------------------------+--------------------------
 Reporter:  luisherranz               |       Owner:  luisherranz
     Type:  enhancement               |      Status:  assigned
 Priority:  normal                    |   Milestone:  6.5
Component:  Editor                    |     Version:  trunk
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+--------------------------

Comment (by hellofromTonya):

 Replying to [comment:24 priethor]:
 > Could we include this in WordPress 6.4 Beta 2? These filters will be
 necessary to further develop the Interactivity API in the next WordPress
 release cycle, and having them in Beta2 is low-risk as they are new and
 not consumed by any core feature.

 As I previously noted, Beta 1 is the cut-off for introducing new
 enhancements and features into Core. See the release process handbook:

 * [https://make.wordpress.org/core/handbook/about/release-cycle/ "How the
 Release Cycle Works"]:
 >**Phase 3: Beta**. Betas are released, and beta testers are asked to
 start reporting bugs. No more commits for new enhancements or feature
 requests are allowed for the rest of the release.

 * [https://make.wordpress.org/core/handbook/about/release-cycle/releasing-
 beta-versions/ Releasing Beta and RC Versions]
 >For Beta releases, ensure that the milestone is cleared of enhancement
 and feature request tickets (e.g., Trac query for 6.1). If there is
 agreement within the release squad that a certain enhancement or feature
 request is critical for the release and thus needs to remain in the
 milestone, its ticket type should be changed to “Task (blessed)”. Also
 ensure with the Editor Tech Lead that enhancements/features merges from
 Gutenberg are similarly either cleared from the milestone or changed to a
 “Task (blessed)”.

 Given the possible impact to 6.5, I started
 [https://wordpress.slack.com/archives/C02RQBWTW/p1695912871640979 a
 consideration discussion] Making WordPress slack `#core` channel. In doing
 so, it broadens the visibility to invite more discussion in case other
 Core contributors and committers think it is necessary to make an
 exception.

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