Skip to content

Clarify validation of custom scalar literals #1156

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

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

Clarify validation of custom scalar literals #1156

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
8efb84c
Exclude custom scalar literals from validation
martinbonnin Apr 2, 2025
f34e98b
Clarify that variables are always allowed when part of a custom scala…
martinbonnin Apr 2, 2025
bf42aa1
add note
martinbonnin Apr 3, 2025
e324a00
Update spec/Section 5 -- Validation.md
martinbonnin Apr 17, 2025
0741216
formatting
martinbonnin Apr 17, 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
Prev Previous commit
Next Next commit
Update spec/Section 5 -- Validation.md
  • Loading branch information
@martinbonnin
martinbonnin authored Apr 17, 2025
commit e324a001acb36a7c913b5ae85b97f985b2c01a18
6 changes: 3 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 @@ -1326,9 +1326,9 @@ the purposes of the "coercible" assertion in this validation rule, we can assume
the runtime value of each {variableUsage} is valid for usage in its position.

Note: Custom scalar coercion rules are not always available when validating a
document and custom scalar literal values are excluded from this validation. If
a custom scalar literal value cannot be coerced, it will raise an execution
error.
document and custom scalar literal values are optional in this validation. If
a custom scalar literal value cannot be coerced, it will raise an error during
execution.

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