fix issue #160: validateVarType parsing numbers #216
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
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 is to fix issue #160, which @f10et ran into as well. Rebased and fixed typo from @f10et in #162
When we find a variable which is
json.Number, depending on the variable type request, we'll extract either the Int64 value, or the float value from thejson.Number.This should work well with gqlgen, which uses the json decoder
UseNumberfunction to decode numbers.https://github.com/99designs/gqlgen/blob/master/graphql/handler/transport/http_get.go#L76
Let me know if I can help make it any better, or if you have any better solution for this problem.