graphiql v3 blog #1308
graphiql v3 blog #1308
Conversation
💻 Website PreviewThe latest changes are available as preview in: https://ade56aab.guild-dev-website.pages.dev |
| @@ -0,0 +1,212 @@ | |||
| --- | |||
| title: GraphiQL 3 Is Here and GraphiQL 4 Is Coming | |||
There was a problem hiding this comment.
I would change the title to something that also gives information about the content
maybe like "GraphiQL v3 is here - React 18, better codebase, balblabla, and you can try v4 alpha with Monaco editor!"
| tags: [graphql, react, graphiql] | ||
| authors: dimitri | ||
| date: 2023-07-01 | ||
| description: GraphiQL 3 was released, here is what was changed and what will be in GraphiQL 4. |
There was a problem hiding this comment.
same here, more information about the content
| most-waited features as integration [monaco-editor](https://github.com/microsoft/monaco-editor) and | ||
| new docs explorer (aka Query Builder) were not introduced. | ||
|
|
||
| After months and months, no progress was made, and I was called to join forces and help the |
There was a problem hiding this comment.
I would make it a bit nicer maybe
Maybe say that you decided to join the team and push all the things on the roadmap
|
|
||
| ### Put Out the Lights on the Christmas Tree 🎄 | ||
|
|
||
| When I started to maintain GraphiQL the first thing first was ESLint improvements, because ESLint |
There was a problem hiding this comment.
maybe add something like that you need good tools and order for good long term maintenance, which is what The Guild is known for
| [#3140](https://github.com/graphql/graphiql/pull/3140) and | ||
| [#3281](https://github.com/graphql/graphiql/pull/3281). | ||
|
|
||
| 1. And |
There was a problem hiding this comment.
I would add here a number of over 150 PRs
| Integration of `monaco-editor` and `monaco-graphql` always was a top priority, since I started | ||
| maintaining this monorepo, but to achieve it, a stable release should be released first ☝️. | ||
|
|
||
| So I decided to propose to release GraphiQL 3 without Reach UI and replace him with maintained |
There was a problem hiding this comment.
| So I decided to propose to release GraphiQL 3 without Reach UI and replace him with maintained | |
| So I proposed releasing GraphiQL v3 with replacing Reach UI with the maintained |
|  | ||
|
|
||
| {/* prettier-ignore */} | ||
| <p className="mt-3 text-center italic">Tab reorders made by |
There was a problem hiding this comment.
I would move that to the previous sentence, something like
In v3 I've also included the tab reorders feature made by @mylesmmurphy
#3111:
|
|
||
| ## GraphiQL 4 🔜 | ||
|
|
||
| 14 months ago the initial issue was created on the integration `monaco-editor` in GraphiQL. |
There was a problem hiding this comment.
I think originally the talk about monaco was many years earlier even
| [`graphiql-prototype`](https://github.com/jonathanawesome/graphiql-prototype) by | ||
| [@jonathanawesome](https://github.com/jonathanawesome)). | ||
|
|
||
| <Callout type="warning"> |
There was a problem hiding this comment.
I would phrase it a bit different and less offensive
Maybe you can say that there was some initial work on Jon on a prototype outside of GraphiQL without integration
| {/* prettier-ignore */} | ||
| <Anchor href="https://deploy-preview-3234--graphiql-test.netlify.app" className="mt-6 block"></Anchor> | ||
|
|
There was a problem hiding this comment.
here is the current high level roadmap we have for GraphiQL, please comment and let us know what you think is missing:
No description provided.