We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
[String]
[]
null
Given this type:
type Test { test1: [String] test2: [String!] test3: [String]! test4: [String!]! }
I'd expect returning nil in each resolver to produce:
nil
{ "data": { "test": { "test1": null, "test2": null, "test3": [], "test4": [] } } }
This is what's returned instead:
{ "data": { "test": { "test1": [], "test2": [], "test3": [], "test4": [] } } }
graphql/graphql-spec#171 for context.
Is this an error or by design? Thanks in advance.
The text was updated successfully, but these errors were encountered:
Looks like a bug. Go treats nils like empty arrays so it would be an easy one to make.
Sorry, something went wrong.
Same problem here! Any update about it? 😞
No branches or pull requests
Expected Behaviour
Given this type:
I'd expect returning
nil
in each resolver to produce:Actual Behavior
This is what's returned instead:
graphql/graphql-spec#171 for context.
Is this an error or by design? Thanks in advance.
The text was updated successfully, but these errors were encountered: