You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found old issues (#651 & #303) that suggest this was fixed at some point, but it looks like it is broken again. With "tracing.hideTracingResponse" set to either true or false, all extensions are hidden from the results window in version 1.6.0
This issue pertains to the following package(s):
GraphQL Playground - Electron App
GraphQL Playground HTML
GraphQL Playground
GraphQL Playground Express Middleware
GraphQL Playground Lambda Middleware
GraphQL Playground Koa Middleware
GraphQL Playground Hapi Middleware
What OS and OS version are you experiencing the issue(s) on?
macOS 10.13.5
What version of graphql-playground(-electron/-middleware) are you experiencing the issue(s) on?
graphql-playground-middleware-koa
What is the expected behavior?
I see the complete response in the result window
What is the actual behavior?
The result window response does not match the network response, specifically, it swallows the extensions: { duration } object.
I can confirm that in Apollo Server 2.0, which pulls in @apollographql/[email protected], the traces never appear no matter the setting of that config option.
I found old issues (#651 & #303) that suggest this was fixed at some point, but it looks like it is broken again. With
"tracing.hideTracingResponse"
set to eithertrue
orfalse
, all extensions are hidden from the results window in version1.6.0
This issue pertains to the following package(s):
What OS and OS version are you experiencing the issue(s) on?
macOS 10.13.5
What version of graphql-playground(-electron/-middleware) are you experiencing the issue(s) on?
graphql-playground-middleware-koa
What is the expected behavior?
I see the complete response in the result window
What is the actual behavior?
The result window response does not match the network response, specifically, it swallows the
extensions: { duration } object.
What steps may we take to reproduce the behavior?
Minimal example:
The text was updated successfully, but these errors were encountered: