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

Make semantic non-null the default? #1122

Open
martinbonnin opened this issue Oct 30, 2024 · 0 comments
Open

Make semantic non-null the default? #1122

martinbonnin opened this issue Oct 30, 2024 · 0 comments

Comments

@martinbonnin
Copy link
Contributor

This is a follow up from #63.

GraphQL best practices are currently to use nullable types by default.

With all the work going on in the nullability working group and the advent of semantic non null types, feels like now is a good time to revisit. Should semantically non null types be the default?

This issue is for gathering community feedback and use cases. Would you rather keep the current nullable by default best practice? Or change it to semantically non null by default? Let us know below or come discuss at the next nullability wg meeting!

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