-
Notifications
You must be signed in to change notification settings - Fork 842
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Aliased pointer types become pointer addresses #488
Comments
atombender
added a commit
to atombender/graphql
that referenced
this issue
Jun 14, 2019
with "type MyInt int", values of type MyInt and *MyInt should be treated as ints. Fixes graphql-go#488.
atombender
added a commit
to atombender/graphql
that referenced
this issue
Jun 14, 2019
with "type MyInt int", values of type MyInt and *MyInt should be treated as ints. Fixes graphql-go#488.
atombender
added a commit
to atombender/graphql
that referenced
this issue
Jun 14, 2019
with "type MyInt int", values of type MyInt and *MyInt should be treated as ints. Fixes graphql-go#488.
atombender
added a commit
to atombender/graphql
that referenced
this issue
Jun 14, 2019
with "type MyInt int", values of type MyInt and *MyInt should be treated as ints. Fixes graphql-go#488.
simaotwx
pushed a commit
to toowoxx/go-graphql
that referenced
this issue
Mar 15, 2021
with "type MyInt int", values of type MyInt and *MyInt should be treated as ints. Fixes graphql-go#488. Signed-off-by: Simao Gomes Viana <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Test case:
This prints
instead of the expected:
Annoyingly, there's no way to work around this by implementing
MarshalJSON
onValue
, since it seems graphql-go doesn't use it.I'll see if I can create a PR.
Related to #199.
The text was updated successfully, but these errors were encountered: