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

Support for null values #683

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Conversation

krasish
Copy link

@krasish krasish commented Nov 14, 2023

Description:

Currently, null values are explicitly ignored and cause an error when parsing. This is not correct, because the GraphQL spec supports them. (ref).

There are also quite a few open issues which refer to this problem, namely:

This PR provides support for null values. I tried to keep the implementation maximally "compliant" with the current codebase, but I am willing to make changes, just to merge this functionality.

I assume that this project is already being used in quite a few production cases and such deviations from the spec are not acceptable. I see that there already are some PRs that introduce this change, which are outdated, I will try to keep mine up-to-date, just to get this merged.

@coveralls
Copy link

Coverage Status

coverage: 91.688% (-0.4%) from 92.051%
when pulling c0f6a48 on krasish:support-nulls
into 4ebf270 on graphql-go:master.

@krasish
Copy link
Author

krasish commented Nov 14, 2023

@sogko @chris-ramon please take a look at this 🙏

@jorgerasillo
Copy link

@sogko or @chris-ramon any chance y'all can get a review on this?

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.

None yet

3 participants