Server directive processing: Process only root blocks

[cbravobernal]

Co-authored with @luisherranz

What?

Create a "root blocks" identifier, so the Interactivity API will only process the directives of these ones.
When we process the directives in PHP of a block that contains inner blocks, we already have the entire HTML, so, in order to prevent the function to run on a inner block render, we need a function to retrieve only the root blocks.

Testing Instructions

Unit tests are included in the PR

Testing Instructions for Keyboard

Screenshots or screencast

[github-actions]

This pull request has changed or added PHP files. Please confirm whether these changes need to be synced to WordPress Core, and therefore featured in the next release of WordPress.

If so, it is recommended to create a new Trac ticket and submit a pull request to the WordPress Core Github repository soon after this pull request is merged.

If you're unsure, you can always ask for help in the #core-editor channel in WordPress Slack.

Thank you! ❤️

View changed files

❔ lib/experimental/interactivity-api/directive-processing.php
❔ phpunit/experimental/interactivity-api/directive-processing-test.php

[luisherranz]

Let's get rid of the global. We can use the same pattern we used here, with a function hooked to render_block_data that has some static variables that are passed down to a second function created inside the first one and hooked to the render_block filter.

[cbravobernal]

Sure, I'll update it and ping when is ready.

[github-actions]

Flaky tests detected in 72686e2.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/6796476784
📝 Reported issues:

• [Flaky Test] should partially select with shift + click (@webkit) #53524 in /test/e2e/specs/editor/various/multi-block-selection.spec.js

[luisherranz]

The e2e interactive tests are failing.

[luisherranz]

The e2e tests should be fixed now.

On second thought, I don't love this unit test because it's coupled with the implementation and won't be useful when we switch to processing the directives using other methods, but I think it's good enough for now.

Let's merge this to keep things moving 🙂

[youknowriad]

Has this been backported to Core already?

[luisherranz]

Yesss.