Draft
Conversation
- Experiment with the WP streaming block parser
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR experiments with the new WP streaming block parser introduced with WordPress 6.9.
This block parser presents a streaming interface to walk through a document and analyze or modify the block structure. So far, the way of doing that was through the
parse_blocks()function. Callingparse_blocks()converts the entire post into a large nested array of block information that contains two copies of every span of HTML from the input . All of this work can lead to some surprisingly heavy parsed documents. Further, because block structure is inherently nested, any code wanting to traverse all of the blocks in a document needs to create its own form of recursion to iterate through the output ofparse_blocks(). The block parser was designed for cases whereparse_blocks()would otherwise perform unnecessary work.In this particular experiment, I use the block parser to replace the
parse_blocks()function and a (somewhat complex) recursive function in its task of detecting a YouTube player on the current page.Testing
/assets/build/lite-yt-embed.jsfile was enqueued.