-
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
Consider integrating graphiql-explorer #11602
Comments
Hey @kolya-ay
Would you be interested? 🙂 |
I was interested in this, but after some digging around looks like when this graphql/graphql-playground#943 is fixed, gatsby will have the graphiql-explorer |
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. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open! 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. Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m Thanks again for being part of the Gatsby community! |
This would be a big DX improvement, re-opening. Sort-of related issue at #14212 |
Looks like OneGraph is working on some improvements, as well -> https://www.youtube.com/watch?v=yWjCAjpHRt0 |
PR adding graphiql-explorer support is open - #14280 |
|
It looks very useful for exploring Gatsby internals.
The text was updated successfully, but these errors were encountered: