Skip to content

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