Skip to content

fix: input object with a nullable field set to null was being removed… #631

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

chirino
Copy link

@chirino chirino commented May 6, 2022

… from the Args map given to a resolver.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.001%) to 91.993% when pulling 7c76e23 on chirino:preserve-nil-input-fields into f02a1c9 on graphql-go:master.

@ki4jnq
Copy link

ki4jnq commented Jun 16, 2022

👍 Running into this on our project, too. Seems there's an existing issue as well, #629

@adaam2
Copy link

adaam2 commented Nov 29, 2022

Can this be merged as we are also running into this?

@kindermax
Copy link

Hi, what chances are that this PR could be merged?

@adaam2
Copy link

adaam2 commented May 23, 2024

@kindermax As far as I can remember, I don't think that this PR is a complete implementation of nulls - we ended up forking this repo and doing it ourselves but I've since left that company so not sure I have access anymore.

@kindermax
Copy link

I see( Well for now I've overcome this by passing variables via context but it is a dirty hack.

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

Successfully merging this pull request may close these issues.

5 participants