graphql / graphql/graphiql

Playground feature parity

Open
#3,951 2 comments 5 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
16.9k
Forks
1.9k
Avg merge
22h 45m
Merged PRs (30d)
70

Description

This is a follow up from https://github.com/graphql/graphql-wg/issues/1648. The current situation of having 2 different IDEs is confusing. Playground hasn't had much activity lately and it'd be grand to consolidate everything in GraphiQL.

That being said, as a Playground user, there are several aspects that I like better there and I'm curious what the team thoughts are about them.

The full context is in https://github.com/graphql/graphql-wg/issues/1648 but the most important ones are:

* [ ] Copy as curl
* [ ] SDL/JSON download
* [ ] Editable endpoint url
* [ ] Multi column schema doc
* [ ] Search the docs
* [ ] Maybe schema polling? (I would have expected this to be available but didn't find it)
* [ ] Settings editor

This is all from a cursory look of comparing the sample index.html ([playground](https://github.com/graphql/graphql-playground/blob/main/packages/graphql-playground-html/minimal.html), [graphiql](https://github.com/graphql/graphiql/blob/main/examples/graphiql-cdn/index.html)). It may very well be that GraphiQL has all those features but that they require more configuration, it which case, some better defaults would be very welcome.

Any thoughts?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.