fix(graphql): blocks return null with select: true#15464
Merged
PatrikKozak merged 5 commits intomainfrom Feb 3, 2026
Merged
Conversation
Contributor
📦 esbuild Bundle Analysis for payloadThis analysis was generated by esbuild-bundle-analyzer. 🤖 |
…-blocks-select-null
…-blocks-select-null
JarrodMFlesch
approved these changes
Feb 3, 2026
Contributor
|
🚀 This is included in version v3.75.0 |
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.
What
GraphQL queries with
select: truewere returning null for block fields and throwing "Cannot return null for non-nullable field" errors.Why
The selection builder wasn't nesting block field selections under their block slug when processing inline fragments. It was creating
{ contentField: { text: true } }instead of{ contentField: { content: { text: true } } }, so the database projection couldn't find the fields.How
blockSlugto GraphQL block type extensions so we can identify block typesFixes #15460