From 1a818fc9c779d36ebcddf08d6c5ccf83a56a4a9b Mon Sep 17 00:00:00 2001 From: Benjie Gillam Date: Fri, 19 May 2023 16:03:18 +0100 Subject: [PATCH] Clarify that selection sets cannot be empty --- spec/Section 3 -- Type System.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/spec/Section 3 -- Type System.md b/spec/Section 3 -- Type System.md index bb0d50b35..d32b08566 100644 --- a/spec/Section 3 -- Type System.md +++ b/spec/Section 3 -- Type System.md @@ -1796,8 +1796,9 @@ to denote a field that uses a Non-Null type like this: `name: String!`. **Nullable vs. Optional** Fields are _always_ optional within the context of a selection set, a field may -be omitted and the selection set is still valid. However fields that return -Non-Null types will never return the value {null} if queried. +be omitted and the selection set is still valid (so long as the selection set +does not become empty). However fields that return Non-Null types will never +return the value {null} if queried. Inputs (such as field arguments), are always optional by default. However a non-null input type is required. In addition to not accepting the value {null},