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.

Sign up for GitHub

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

Jump to bottom

Support null literal for optional fields #135

Open
paulfthomas opened this issue Mar 20, 2019 · 1 comment
Open

Support null literal for optional fields #135

paulfthomas opened this issue Mar 20, 2019 · 1 comment
Labels
feature-request Request a new feature

Comments

@paulfthomas
Copy link

Not sure if it's a bug or a missing feature but null literals don't seem to work.
Passing null to an optional field for a mutation results in the field being ignored.

It's been added to GraphQL, see graphql/graphql-spec#83
@minbi minbi self-assigned this Mar 25, 2019
@minbi minbi added the AppSync label Mar 25, 2019
@minbi
Copy link
Contributor

minbi commented Mar 25, 2019

Hi @paulfthomas ,

We'll need to look into this. Thanks for the report.

@desokroshan desokroshan assigned desokroshan and unassigned minbi Apr 15, 2019
@desokroshan desokroshan added the feature-request Request a new feature label Apr 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature-request Request a new feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jamesonwilliams @desokroshan @minbi @paulfthomas