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

SemanticNullability -> SemanticNullabilityType; add precision #1661

Closed
wants to merge 2 commits into from
Closed

SemanticNullability -> SemanticNullabilityType; add precision #1661

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
37c6277
Make the problem statement more precise
benjie Feb 18, 2025
3d7b56a
Update gitignore
benjie Feb 18, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .prettierignore
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
agendas/*/*.md
agendas/*/*/*.md
rfcs/SemanticNullability.md
rfcs/SemanticNullabilityType.md
11 changes: 8 additions & 3 deletions rfcs/SemanticNullability.md → rfcs/SemanticNullabilityType.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# RFC: Semantic Nullability
# RFC: Semantic Nullability Type

# 📜 Problem History

Expand Down Expand Up @@ -166,8 +166,13 @@ non-null" type.

# 📜 Problem Statement

GraphQL needs to be able to represent semantically nullable and semantically
non-nullable types as such when error propagation is disabled.
GraphQL schema authors need a way to explicitly distinguish between
**semantically nullable** (where `null` is a meaningful application-level
value), **semantically non-nullable** (where `null` should not be expected but
might still occur due to errors), and **strictly non-nullable** (where `null`
must never appear, even in the presence of errors). This distinction ensures
that schemas accurately convey application intent while defining appropriate
error boundaries when error propagation is enabled.

# 📋 Solution Criteria

Expand Down