@@ -90,7 +90,7 @@ LineTerminator ::
90
90
Like white space, line terminators are used to improve the legibility of source
91
91
text and separate lexical tokens, any amount may appear before or after any
92
92
other token and have no significance to the semantic meaning of a GraphQL
93
- Document. Line terminators are not found within any other token.
93
+ Document.
94
94
95
95
Note: Any error reporting which provides the line number in the source of the
96
96
offending syntax should use the preceding amount of {LineTerminator} to produce
@@ -358,8 +358,8 @@ piece of information available to request within a selection set.
358
358
Some fields describe complex data or relationships to other data. In order to
359
359
further explore this data, a field may itself contain a selection set, allowing
360
360
for deeply nested requests. All GraphQL operations must specify their selections
361
- down to fields which return scalar values to ensure an unambiguously shaped
362
- response.
361
+ down to fields which return scalar or enum values (or lists of those types)
362
+ to ensure an unambiguously shaped response.
363
363
364
364
For example, this operation selects fields of complex data and relationships
365
365
down to scalar values.
@@ -668,7 +668,7 @@ be present and `likers` will not. Conversely when the result is a `Page`,
668
668
InlineFragment : ... TypeCondition? Directives? SelectionSet
669
669
670
670
Fragments can be defined inline within a selection set. This is done to
671
- conditionally include fields based on their runtime type. This feature of
671
+ conditionally include fields based on parent object's runtime type. This feature of
672
672
standard fragment inclusion was demonstrated in the ` query FragmentTyping `
673
673
example. We could accomplish the same thing using inline fragments.
674
674
@@ -1171,8 +1171,8 @@ VariableDefinition : Variable : Type DefaultValue? Directives[Const]?
1171
1171
1172
1172
DefaultValue : = Value[ Const]
1173
1173
1174
- A GraphQL operation can be parameterized with variables, maximizing reuse, and
1175
- avoiding costly string building in clients at runtime .
1174
+ A GraphQL operation can be parameterized with variables
1175
+ maximizing reuse of parsed queries by the GraphQL service .
1176
1176
1177
1177
If not defined as constant (for example, in {DefaultValue}), a {Variable} can be
1178
1178
supplied for an input value.
0 commit comments