fix: Fix error handling for input values #62
Merged
Conversation
This file contains 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
stuebingerb
force-pushed
the
fix/fix-input-validation
branch
from
50bea56 to
c77a31c
Compare
This resolves #59 and some related issues with error handling. In particular: - Providing incorrect data types for input values (e.g. an object for a list) no longer causes HTTP 500 responses but results in proper GraphQL errors - Existing validation for list values no longer show "type null" but "type List" - Lists and enum values in error messages no longer show object references but their actual values
stuebingerb
force-pushed
the
fix/fix-input-validation
branch
from
c77a31c to
cf557ab
Compare
mervyn-mccreight
approved these changes
Nov 8, 2024
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.
This resolves #59 and some related issues with error handling. In particular: