feat: add support for resolving PostContent blocks #326
+112
−1
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 for resolving
innerBlocks
forcore/post-content
blocks.Important
This PR is based off of #324, which should be merged first.
Relevant diff: 8e2e921
Why
This is essential for supporting FSE, and due to the
final
/private
nature ofContentBlocksResolver
cannot be easily hooked in from external code.While the WPGraphQL core does not (yet) support querying for a complete FSE template (where
core/post-content
is traditionally used, I believe the above consideration along with the following reasons still make this a good candidate for inclusion:wpgraphql_content_blocks_resolver_content
, that goes along with validating the@todo
in thePost
model gate*Note: This PR is based on #324 solely to prevent merge conflicts. There are no code dependencies between the commits.