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 the Strict Nullability draft specification #736

Open
kawazoe opened this issue Jan 22, 2025 · 0 comments
Open

Support for the Strict Nullability draft specification #736

kawazoe opened this issue Jan 22, 2025 · 0 comments

Comments

@kawazoe
Copy link

kawazoe commented Jan 22, 2025

The GraphQL consortium recently announced a new draft to support smarter clients when it comes to error handling. The Strict Nullability specification enables clients to distinguish actual null values in responses from null values caused by server side errors.

Currently, many clients like Relay supports a temporary implementation of this feature with the @semanticNonNull directive. While this isn't the final version, and it appears like the final version might move to a different approach with a server side @ extendedNullability directive, it would be useful to support the draft right now to enable to play with the draft version of this specification.

See #735 for other Relay-specific directives related to those changes.

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

No branches or pull requests

1 participant