fix(graphcache): Fix typo in owned data null resolution for resolvers #3371
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.
Resolves #3370
Summary
This fixes a typo in an inverted condition for an owned data check in
resolveResolverResult
. The equivalent check inresolveLink
isisOwnedData && prevData === null
, i.e. when a prior result wasnull
it keeps the field set tonull
.Instead, the resolver did the opposite and hence turned a first resolution of a
prevData === null
result into a nulled value, i.e. preventing subsequent results from succeeding.Set of changes
resolveResolverResult
condition for ownednull
values