1
1
# Validation
2
2
3
- GraphQL service does not just verify if a request is syntactically correct, but also
3
+ A GraphQL service does not just verify if a request is syntactically correct, but also
4
4
ensures that it is unambiguous and mistake-free in the context of a given
5
5
GraphQL schema.
6
6
@@ -13,8 +13,9 @@ Typically validation is performed in the context of a request immediately before
13
13
execution, however a GraphQL service may execute a request without explicitly
14
14
validating it if that exact same request is known to have been validated before.
15
15
For example: the request may be validated during development, provided it does
16
- not later change. Any client-side or development-time
17
- tool should report validation errors and not allow the
16
+ not later change, or a service may validate a request once and memoize the
17
+ result to avoid validating the same request again in the future. Any client-side
18
+ or development-time tool should report validation errors and not allow the
18
19
formulation or execution of requests known to be invalid at that given point in
19
20
time.
20
21
@@ -577,7 +578,7 @@ fragment conflictingDifferingResponses on Pet {
577
578
- Let {selectionType} be the unwrapped result type of {selection}.
578
579
- If {selectionType} is a scalar or enum:
579
580
- The subselection set of that selection must be empty.
580
- - If {selectionType} is an interface, union, object or list of those types :
581
+ - If {selectionType} is an interface, union, or object :
581
582
- The subselection set of that selection must NOT BE empty.
582
583
583
584
** Explanatory Text**
0 commit comments