Skip to content

Commit 6d93d35

Browse files
committed
Merge pull request #49 from gabrielf/introduce-not-null-syntax
Describe how non-null and list types are written earlier.
2 parents 7fcf062 + 1d1a99b commit 6d93d35

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

Section 3 -- Type System.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -663,7 +663,8 @@ type declared by the input field.
663663
A GraphQL list is a special collection type which declares the type of each
664664
item in the List (referred to as the *item type* of the list). List values are
665665
serialized as ordered lists, where each item in the array is serialized as per
666-
the item type.
666+
the item type. To denote that a field uses a List type the item type is wrapped
667+
in square brackets like this: `pets: [Pet]`.
667668

668669
**Result Coercion**
669670

@@ -691,7 +692,9 @@ By default, all types in GraphQL are nullable; the {null} value is a valid
691692
response for all of the above types. To declare a type that disallows null,
692693
the GraphQL Non-Null type can be used. This type declares an underlying type,
693694
and this type acts identically to that underlying type, with the exception
694-
that `null` is not a valid response for the wrapping type.
695+
that `null` is not a valid response for the wrapping type. A trailing
696+
exclamation mark is used to denote a field that uses a Non-Null type like this:
697+
`name: String!`.
695698

696699
**Result Coercion**
697700

0 commit comments

Comments
 (0)