Repository navigation
Conversation
Collaborator
|
thanks for your contributation |
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
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.
Fixes #315
Literal descriptions currently render Boolean values as Python
True/Falseand omit legal null values. Clients relying on the schema description can consequently construct invalid GraphQL input or incorrectly reject null.true/false, preserving string and numeric members.literal_allowed_values' public return contract unchanged.The helpers now live in
graphql/type_mapping.pyand are shared by both schema paths, so the fix is made there rather than incompose_schema.py.Validation (Python 3.12.14):
python -m pytest tests/graphql tests/use_case -q: 424 passed, 2 skipped.git diff --check: passed.AI-assisted implementation. No claim of validation on other Python versions or of running the repository-wide suite.