-
Notifications
You must be signed in to change notification settings - Fork 827
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
allow null in input list #749
Comments
In this case I could just use a string with comma-separated values:
But I would lose some type safety that way. It seems to me that null would be useful as a legal value in any case. |
@altaurog graphene is powered by graphql-core which is an almost direct port of the graphql-js library for node. graphql-core doesn't support I'm going to close this issue in favour of tracking progress in the graphql-core repo. |
@jkimbo thanks! I’ll have a look there. |
Aforementioned issues have been removed. Is it truly fixed? |
@antwan Graphene v3 uses the new v3 version of graphql-core which has full support for nulls. We’re hoping to release the new version soon but in the meantime there is a beta version that you could use. |
I would like to be able to create a range search parameter as a list of possibly null values, so I could do something like the following:
components (amps: [null, 3])
components (amps: [1, 3])
components (amps: [1, null])
Input List type doesn’t seem to allow this. I get an
Unexpected Name "null"
errorThe text was updated successfully, but these errors were encountered: