Skip to content
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

The default_value of InputField should be INVALID #1111

Merged
merged 3 commits into from
Feb 8, 2020
Merged

The default_value of InputField should be INVALID #1111

merged 3 commits into from
Feb 8, 2020

Conversation

rhizoome
Copy link
Contributor

@rhizoome rhizoome commented Dec 11, 2019

Since GraphQL 3.0 there is a distinction between None and INVALID (no value).
The tests captured the bug and are updated.

See also graphql-python/graphql-core#66 (comment)

I think there are more bugs of this kind, but since I don't know graphene well, yet, I take baby steps.

I could not track the snapshot differences, the order is wrong and master has the same problem too. If master is solved I'll rebase this PR. @jkimbo has the same differences in his commits.

Copy link

@winged winged left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good so far! 💯

Jean-Louis Fuchs and others added 3 commits February 8, 2020 10:55
Since GraphQL 3.0 there is a distinction between None and INVALID (no value).
The tests captured the bug and are updated.
@jkimbo
Copy link
Member

jkimbo commented Feb 8, 2020

@ganwell I've updated your PR to use Undefined instead of INVALID to keep up to date with graphql-core: graphql-python/graphql-core#77

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants