-
Notifications
You must be signed in to change notification settings - Fork 428
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
Support where Null
value came from
#183
Comments
Yes, it seems as if the GraphQL spec and authors changed their stance on I think the easiest change would be to add a tri-state enum like this: enum GraphQLOption<T> {
Absent,
None,
Some(T),
} This would let you continue to use |
Hey, |
This is now supported in master via a |
I wanted to do PATCH operation in GraphQL but came to know that I had to do a workaround like #108 which in my honest opinion makes me write more code for little effect which is no fun.
In that issue, it was stated along with the workaround that :
I counter that with The GraphQL Spec which clearly dictates, though
undefined
is still not supported, an absence ofnull
can be interpreted differently that explicitnull
.So, even though only
Null
value is supported, it would be true to the spec if we would be given the source of the said value, whether it was explicit or implicit.Like:
And may be a helper conversion to
Option<Option<T>>
whereThe text was updated successfully, but these errors were encountered: