Show graphql extensions #813
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
|
|
7 tasks
|
That makes a lot more sense yes. I just don't get why the code was there in the first place, it wasted an hour of my life debugging why tracing wasn't working, because I had never even considered a development tool to just TRASH part of the output. Collapse by default, sure, but delete the entire extensions section... why?!? |
|
@curry684 I had a similar experience. We add additional data to extensions (not tracing) and after updating to |
|
cc @timsuchanek who wrote the extension handling logic |
cgxxv
pushed a commit
to cgxxv/graphql-playground
that referenced
this pull request
Mar 25, 2022
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 #804.
Changes proposed in this pull request:
tracing.hideTracingResponsesetting is enabled, tracing is hidden from the results view as advertised in the docs.