Skip to content

Variable and argument null vs undefined #90

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

Conversation

NeedleInAJayStack
Copy link
Member

This is a follow-up to #87. That PR added support to differentiate between explicitly providing the literal value null and implicitly not providing a value at all in input objects provided in the arguments. This merge request extends that functionality to input objects in variables and non-object arguments.

It also fixes a bug with not pre-validating argument inputs against their type (for example, passing null to a non-null parameter would passed null all the way into the resolver). It also removes force-casts to harden against server-wide fatal errors.

@NeedleInAJayStack
Copy link
Member Author

Hey @paulofaria, since we've removed the ubuntu-16.04 action, could you remove it from the status checks as well? I think you can do so by going to Settings -> Branches -> Require status checks to pass before merging, and uncheck the Ubuntu 16.04 one.

@paulofaria
Copy link
Member

@NeedleInAJayStack great work! Feel free to merge and tag!

@NeedleInAJayStack
Copy link
Member Author

Awesome, thanks @paulofaria!

@NeedleInAJayStack NeedleInAJayStack merged commit e383f79 into GraphQLSwift:master Oct 3, 2021
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.

2 participants