Description
We are happy to announce that GraphQL Playground and GraphiQL are joining forces.
In the next few days a formal blog post will be going out that talks about some of the changes taking place, new features you can expect, and existing ones you can count on staying.
TLDR; you will be able to do everything you were able to do in the latest graphql playground, and hopefully much more
Archiving this Repository
After a few minor bugfixes and a final release, we will archive this repository under the official GraphQL github organization. We will at least try to upgrade codemirror-graphql and the LSP to eliminate a few bugs we've addressed in those underlying packages. You will still be able to fork it and create other projects with it if you like.
Any further issues about the future GraphiQL preset for GraphQL Playground should be created in the graphiql repository for now, and will be fielded by the Playground Preset team. Eventually the playground preset may or may not have it's own repository, or it may join the monorepo. We may also migrate relevant old issues (feature requests especially) from this repo to a new repo for playground
Archiving the Slack Channel
The Prisma Slack channel for Playground will be going away. In its place is a channel on the GraphiQL Discord Group. Check it out here.
Migrating to the Forthcoming Playground GraphiQL Preset
A migration guide will be provided, as some settings will change, but expect a fairly straighforward transition from the previous settings to the new settings format. We will be using graphql-config 3.0, so be sure to pay mind to the new and improved configuration format!
Many of the same settings that the Prisma GraphQL VSCode Extension (which also uses the Official LSP) currently supports will also be supported, such as custom directives, custom scalars, custom types, "hidden" fragments, custom parsing rules and more (further documentation forthcoming).
Call for a Playground Preset Team
The playground preset will need a team of contributors to help develop and maintain the playground specific preset and plugins - the doc explorer, headers tab, tracing, etc.
They will be in charge of managing the entire playground in a product sense as well, and should consult with playground users here to ensure that the product continues to improve at the direction of the graphql playground user community.
Initially, they can help advance the core GraphiQL Plugin API (graphql/graphiql#983) for these purposes, and should be able to begin developing the custom preset as soon as the first [email protected] lands.
Get Updates
If you want to be part of the Playground Preset team, subscribe to graphql/graphiql#1443 and the plugin API meta-issue referenced above