feat: add support for resolving pattern blocks #323
Merged
Conversation
This file contains 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
Co-authored-by: Ta5r <[email protected]>
🦋 Changeset detectedLatest commit: d57adbf The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
2 tasks
justlevine
changed the title
|
Awesome! |
justlevine
deleted the
feat/backporting_populate_pattern_inner_blocks
branch
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.
What
This PR adds support to resolving the
innerBlocksfor synced Block Patterns, introduced in WordPress 6.6Why
While synced patterns are a highlight of FSE, they are still commonly inserted manually into post/page/cpt content, especially in hybrid themes.
Since this is a backwards-compatible improvement, I believe it makes sense to introduce this now instead of after any incoming breaking changes.
How
See diff