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.
Dataloaders now auto-resolves for nullable graphql fields as the default behaviour when resolving the unresolved result for a key.
This is useful when the result is expected to be null, and it's not an exceptional case.
The default behaviour is determined by the Loader decorator on the dataloader`s creation.
If the underlying graphql field, for which the dataloader is created, is nullable - the result can be resolved to null.
Example:
The
callout
is decorated as nullable, so the dataloader will auto-resolve tonull
if the result is not found.You can override this behaviour by setting the
resolveToNull
flag tofalse
. That way the problematic values will always be resolved to errors.