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.

Sign up for GitHub

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

Clarify 'Values of Correct Type' rule relates to literals #1118

Open
wants to merge 8 commits into
base: main
Choose a base branch
from
Open

Clarify 'Values of Correct Type' rule relates to literals #1118

Changes from 2 commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
7fe1b5a
Clarify 'Values of Correct Type' rule does not apply to variables.
benjie Oct 17, 2024
7d86799
Clarify nested variable usages in Values of Correct Type
benjie Oct 17, 2024
d5866f7
Merge branch 'main' into values-of-correct-type-variables
benjie Dec 12, 2024
560a9cb
Change from referenced variable's type to suitable usage in its position
benjie Dec 12, 2024
ee80b36
Further editing
benjie Dec 12, 2024
daf28a2
The assumption is only valid locally.
benjie Dec 12, 2024
14e7c91
Merge branch 'main' into values-of-correct-type-variables
benjie Jan 9, 2025
7d9baa9
coercibility -> coercible to pass spell check
benjie Jan 9, 2025
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
15 changes: 12 additions & 3 deletions spec/Section 5 -- Validation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1303,14 +1303,23 @@ fragment resourceFragment on Resource {

**Formal Specification**

- For each input Value {value} in the document:
- For each literal Input Value {value} in the document:
- Let {type} be the type expected in the position {value} is found.
- {value} must be coercible to {type}.
- {value} must be coercible to {type} (with the assumption that any
{variableUsage} nested within {value} will represent a runtime value of the
referenced variable's type).

**Explanatory Text**

Literal values must be compatible with the type expected in the position they
are found as per the coercion rules defined in the Type System chapter.
are found as per the coercion rules defined in the Type System chapter. Variable
values are handled by the rule
[All Variable Usages Are Allowed](#sec-All-Variable-Usages-Are-Allowed).
{ListValue} and {ObjectValue} may nest additional Input Values, some of which
may be a {variableUsage}. Each nested {variableUsage} will be coerced during
execution - see [Coercing Variable Values](#sec-Coercing-Variable-Values) - thus
we assume their runtime value will coerce to the type of the referenced
variable.

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