V2 monaco rewrite - Needs Maintainers & Contributors!

[acao]

I apologize how neglected this repository has been! We have many co-maintainers who are all busy with work and maintaining other graphql ecosystem tooling. 🥵

We had planned on merging graphiql and playground projects, but it no longer seems to be a good idea. At the time I was a paid open source maintainer for GraphiQL, Vscode Graphql and the language server, however the pandemic has changed all of that.

The best we can hope for is that they can share some react components & utilities via our forthcoming @graphiql/react sdk! Most importantly, whatever is in playground’s future, it will be using our new monaco-graphql! 💫

Our focus now is on the graphiql rewrite, but there is nothing stopping anyone from starting with monaco-graphql and react on a new playground.

Proposals that convert the existing playground to use monaco-graphql are also welcome. We don’t have a roadmap for this approach.

If anyone has been particularly helpful and knowledgeable helping with issues, creating PRs for important bugs, etc, feel free to nominate them as potential maintainers in the comments! Self nominations are also of course welcome.

[acao]

One of the most confusing parts about maintaining this repository is that many issues are for forks of playground such as apollo’s fork (which has issues disabled), or embedded implementations in various frameworks or platforms with edge case or outdated implementations.

it deserves a dedicated team!

[jspizziri]

GraphQL Playground & GraphiQL Are No Longer Merging

We've decided it no longer makes sense to merge the projects, though they will continue to use tons of shared logic in the form of the editor mode. It made sense at the time that Prisma offered playground to us, but it's clear the community wants to move this project forward.

Just for clarity (given the above linked issue)

[BeauBouchard]

@acao and @jspizziri I am interested in being a maintainer.

If there are still opportunities to improve this repo and prioritize work I would be happy to help.

[acao]

@dotansimha ^^ !! :)

[timsuchanek]

Hey everyone, a quick update here:
GraphiQL 1 will soon have tabs.
We just had the GraphiQL WG meeting. Recording coming soon.

We have just agreed on a new design for the new GraphiQL 2, as proposed here.

With the tabs, we're basically getting to feature parity between GraphiQL and the Playground.

I suggest, that we leave the playground for now as it is, as GraphiQL will cover the same needs moving forward.
Once we have the GraphiQL 2 out, let's reassess, but I think it would make more sense to potentially launch a Playground v2, which is either re-exporting or reusing the GraphiQL implementation.

[dotansimha]

fyi @n1ru4l ;)

[AaronNGray]

@acao, @timsuchanek is it possible to get Playground installing/building again theres multiple versioning issues, as I need a graphql queryer that does graphql-ws and I need it like yesterday. So if it would be possible to get it building again and with @ardatan's pull request #1295 even as a branch it would be great !