fix: add timeline trace visibility for failed GraphQL introspection queries#9736
Open
BloodShop wants to merge 2 commits intoKong:developfrom
Open
fix: add timeline trace visibility for failed GraphQL introspection queries#9736BloodShop wants to merge 2 commits intoKong:developfrom
BloodShop wants to merge 2 commits intoKong:developfrom
Conversation
…ueries - Enhanced fetchGraphQLSchemaForRequest to include response data in all error cases - Added 'Show Trace' button that appears when introspection fails with timeline data - Integrated ResponseTimelineViewer to display request/response details inline - Users can now debug authentication issues, server errors, and other introspection failures - Maintains backward compatibility with existing error handling Fixes Kong#5776
|
|
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
2 participants
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
This PR fixes issue #5776 by making GraphQL introspection query traces available when they fail, enabling users to debug authentication and server issues.
Problem
When GraphQL introspection queries failed, users had no access to request/response details, making it impossible to debug authentication issues, server errors, or misconfigurations.
Solution
fetchGraphQLSchemaForRequestto include response data containing timeline pathsResponseTimelineViewercomponent to display full request/response details inlineBenefits
Testing
Tested with GraphQL endpoints that:
Files Modified
packages/insomnia/src/ui/components/editors/body/graph-ql-editor.tsxFixes #5776