Nested resolver bug replication #5433
Open
Conversation
This file contains 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
|
|
In additional resolvers, returned type should match the type of the field of the resolver. Otherwise, |
ardatan
force-pushed
the
master
branch
4 times, most recently
from
72ed5cd to
fbf068b
Compare
ardatan
force-pushed
the
master
branch
2 times, most recently
from
b78fdb4 to
a1bfc49
Compare
ardatan
force-pushed
the
master
branch
2 times, most recently
from
f6b9ba0 to
4d52840
Compare
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.
Description
Replication case, resolver inside an
additionalResolversonly receives__typename, and no data from the responsecontext.Swapi.Query.pet_by_petIdreturnsWhen the upstream server returns
{ "id": "0fc9111f-570d-4ebe-a72e-ff4eb274bc65", }