Fix GraphQL response parsing for pathless errors#404
Open
jstar0 wants to merge 1 commit into
Open
Conversation
c693d7a to
dcc5d8e
Compare
18488292860-coder
suggested changes
Jun 21, 2026
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.
Summary
Fix GraphQL MCP response parsing for valid GraphQL API responses that omit optional
error metadata. This keeps the tool from replacing actionable API messages with a
Zod
invalid_unionvalidation dump.Fixes #402.
Changes
path,locations, andextensionscan beomitted or null where GraphQL permits it.
errorsfield.path: nullerrors withcustom extensions, and successful responses without
errors.Verification