Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit df483ec

Browse files
committedOct 17, 2024·
Clarify 'Values of Correct Type' rule does not apply to variables.
1 parent 7073e3a commit df483ec

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed
 

‎spec/Section 5 -- Validation.md

+4-2
Original file line numberDiff line numberDiff line change
@@ -1303,14 +1303,16 @@ fragment resourceFragment on Resource {
13031303

13041304
**Formal Specification**
13051305

1306-
- For each input Value {value} in the document:
1306+
- For each literal input Value {value} in the document:
13071307
- Let {type} be the type expected in the position {value} is found.
13081308
- {value} must be coercible to {type}.
13091309

13101310
**Explanatory Text**
13111311

13121312
Literal values must be compatible with the type expected in the position they
1313-
are found as per the coercion rules defined in the Type System chapter.
1313+
are found as per the coercion rules defined in the Type System chapter. Variable
1314+
values are handled by the rule
1315+
[All Variable Usages Are Allows](#sec-All-Variable-Usages-Are-Allowed).
13141316

13151317
The type expected in a position includes the type defined by the argument a
13161318
value is provided for, the type defined by an input object field a value is

0 commit comments

Comments
 (0)
Please sign in to comment.