Allow nullable & optional variables and variables with default values #2949
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
martinbonnin
force-pushed
the
nullable-optional-variables
branch
from
e7e7a47
to
fb71bfe
Compare
sav007
approved these changes
Feb 25, 2021
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.
Allow optional variables (the ones that can be absent) to have a "null" value.
This is something that has been discussed a lot and is confusing because GraphQL doesn't really make the distinction between "optional" and "nullable" for input values in the type system. But it should still be possible to differentiate between "absent" and "null" at runtime. See graphql/graphql-spec#418 (comment)
Also make variables with a default variable optional. See #2686