Fix graphql wrapping types #392
Merged
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
kurayama
force-pushed
the
bugfix/wrapping-types
branch
from
da907b2
to
1c0ac6c
Compare
rochdev
requested changes
Dec 10, 2018
kurayama
force-pushed
the
bugfix/wrapping-types
branch
from
1c0ac6c
to
4bf1c9a
Compare
rochdev
approved these changes
Dec 10, 2018
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.
This PR fixes wrapping field resolvers when using more than one level of wrapping types. E.g. [Type!]!
It follows a similar way to get the named type as in graphql-js.