-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clicking “schema” in the GraphQL Playground crashes the page #25128
Comments
Hi, thanks for the issue! I don't think that we'll fix this as the GraphQL playground always has been behind a flag (on purpose) and soon will be deprecated: graphql/graphql-playground#1143 The GraphiQL explorer that comes by default with Gatsby has more capabilities than GraphQL playground and soon will also have complete feature parity with it. We'll also remove the GraphQL playground option in the upcoming v3 of Gatsby. Feel free to dig into the issue and send in a PR but it's not our priority to fix this. Thanks! |
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. Thanks for being a part of the Gatsby community! 💪💜 |
Hey again! It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Thanks again for being part of the Gatsby community! 💪💜 |
I will go back to normal graphql for now, but I get this same issue:
|
Description
When on the GraphQL Playground page, clicking the “schema” link on the side crashes the page.
Steps to reproduce
Demo project (just the output of
gatsby-cli new
): https://github.com/johnridesabike/gatsby-playground-demonpx gatsby-cli new gatsby-playground-demo cd gatsby-playground-demo GATSBY_GRAPHQL_IDE=playground npm run start
Open http://localhost:8000/___graphql (I tested in Safari, Firefox, and Chrome with the same result)
Click “schema” (on the right side)
Expected result
Display the schema (and not crash).
Actual result
Page goes blank. This is logged in the browser console:
Environment
The text was updated successfully, but these errors were encountered: