fix(gatsby): Add early return in link resolver for empty arrays #20068
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.
Why
Consider a schema like,
And a query like,
If a collection has no items, this currently returns
items
set tonull
as opposed to[]
(even if it is non nullable as shown in the schema above).Why
This happens because the link resolver sets the
{ in: value }
operator in case the field value is an array. This however doesn't make sense for an empty array.This PR adds an early return to fix this 🙂
Todo
Related issues
@Simply007 discovered this issue when building
gatsby-source-kentico
. You can find a reproduction at https://github.com/Simply007/gatsby-null-instead-of-array