Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add note above variables to Values of Correct Type rule #1113

Closed
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions spec/Section 5 -- Validation.md
Original file line number Diff line number Diff line change
Expand Up @@ -1307,6 +1307,15 @@ fragment resourceFragment on Resource {
- Let {type} be the type expected in the position {value} is found.
- {value} must be coercible to {type}.

Note: Because all variable usages must be allowed,
[as specified below separately](#sec-All-Variable-Usages-Are-Allowed), it can be
assumed that any variables found within input Values are within allowed
positions. Because variable values are supplied only at runtime, validation of
the supplied values is deferred to the {CoerceVariableValues()} algorithm
[as part of execution](#sec-Coercing-Variable-Values). For the purpose of this
algorithm, it can therefore be assumed that all variables found within input
Values in a document are coercible.

**Explanatory Text**

Literal values must be compatible with the type expected in the position they
Expand Down
Loading