At a glance
- Identifier: #1157
- Stage: RFC X / Superseded
- Champion: @martinbonnin
- Latest activity: Marked as Superseded on 2025-06-12
- Spec PR: https://github.com/graphql/graphql-spec/pull/1157
- Related:
Spec PR description
See https://github.com/graphql/graphql-spec/pull/1118/files#r2023188399
When validating a document, the custom scalar coercion rules are not always known. In those cases, it's impossible to validate them.
For an example, with this operation, it's impossible to detect that "InvalidDate" is not a valid Date without knowledge of the coercing rules:
{
events(after: "InvalidDate") {
title
startsAt
}
}
I think (but wouldn't bet on it) that this is already the case in graphql-js for an example?
Excluding those from the validation feels like a better reflection of the current state of things albeit probably a spec change.
Timeline
June 2025
- Marked as Superseded on 2025-06-12 by benjie
April 2025
- Spec PR closed on 2025-04-03
- Advanced to RFC 0 on 2025-04-03 by benjie
- Spec PR created on 2025-04-02 by martinbonnin
- @martinbonnin committed "Exclude custom scalar literals from validation" on 2025-04-02