Problem: passing input object as a resolved class doesn't work #249
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
ValueResolver makes an assumption that an object passed through is always going to be a map. However, when using graphql-java with graphql-java-annotations and graphql-java-servlet (GraphQLVariables), the inputs passed through are already resolved. Solution: this patch allows to pass such objects through the resolver unmodified, without throwing an exception.
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.
ValueResolver makes an assumption that an object passed through
is always going to be a map.
However, when using graphql-java with graphql-java-annotations and
graphql-java-servlet (GraphQLVariables), the inputs passed through
are already resolved.
Solution: this patch allows to pass such objects through the resolver
unmodified, without throwing an exception.