Skip to content

Commit a5cc6ea

Browse files
authored
Clarify that selection sets cannot be empty (#1025)
1 parent afc0a35 commit a5cc6ea

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

spec/Section 3 -- Type System.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1796,8 +1796,9 @@ to denote a field that uses a Non-Null type like this: `name: String!`.
17961796
**Nullable vs. Optional**
17971797

17981798
Fields are _always_ optional within the context of a selection set, a field may
1799-
be omitted and the selection set is still valid. However fields that return
1800-
Non-Null types will never return the value {null} if queried.
1799+
be omitted and the selection set is still valid (so long as the selection set
1800+
does not become empty). However fields that return Non-Null types will never
1801+
return the value {null} if queried.
18011802

18021803
Inputs (such as field arguments), are always optional by default. However a
18031804
non-null input type is required. In addition to not accepting the value {null},

0 commit comments

Comments
 (0)