Add support for literal boolean and string types#214
Merged
captbaritone merged 1 commit intomainfrom Jan 26, 2026
Merged
Conversation
- Literal `true`/`false` types now infer to `Boolean` in output positions - Literal string types (e.g., `"hello"`) now infer to `String` in output positions - Literal types in input positions (arguments, input type fields) produce a helpful error explaining that GraphQL cannot enforce specific literal values - Numeric literal types (e.g., `42`, `3.14`) produce a specific error about being ambiguous between Int and Float, similar to the `number` type Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
✅ Deploy Preview for grats ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
true/falsetypes now infer toBooleanin output positions (field return types)"hello") now infer toStringin output positions42,3.14) produce a specific error about being ambiguous betweenIntandFloat, similar to thenumbertypeTest plan
🤖 Generated with Claude Code