From 37c627745ac3c07164994be04ed2a9f6c0353cf4 Mon Sep 17 00:00:00 2001 From: Benjie Gillam Date: Tue, 18 Feb 2025 09:19:50 +0000 Subject: [PATCH 1/2] Make the problem statement more precise --- ...anticNullability.md => SemanticNullabilityType.md} | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) rename rfcs/{SemanticNullability.md => SemanticNullabilityType.md} (97%) diff --git a/rfcs/SemanticNullability.md b/rfcs/SemanticNullabilityType.md similarity index 97% rename from rfcs/SemanticNullability.md rename to rfcs/SemanticNullabilityType.md index 530415fa..c4f7de00 100644 --- a/rfcs/SemanticNullability.md +++ b/rfcs/SemanticNullabilityType.md @@ -1,4 +1,4 @@ -# RFC: Semantic Nullability +# RFC: Semantic Nullability Type # 📜 Problem History @@ -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 From 3d7b56a1defab3f2ab63bc90a70f7ed54c816c54 Mon Sep 17 00:00:00 2001 From: Benjie Gillam Date: Tue, 18 Feb 2025 10:05:09 +0000 Subject: [PATCH 2/2] Update gitignore --- .prettierignore | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.prettierignore b/.prettierignore index e6f8b7e7..a616c9e8 100644 --- a/.prettierignore +++ b/.prettierignore @@ -1,3 +1,3 @@ agendas/*/*.md agendas/*/*/*.md -rfcs/SemanticNullability.md +rfcs/SemanticNullabilityType.md