Repository navigation
Add the GraphiQL 6 release post - #2568
trevor-scheer wants to merge 2 commits into
Conversation
|
@trevor-scheer is attempting to deploy a commit to the The GraphQL Foundation Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
benjie
left a comment
There was a problem hiding this comment.
Awesome! Here's some feedback, but I think this is fine to post as-is.
|
|
||
| GraphiQL 6 brings a completely redesigned workspace, along with new tools for building operations and saving operations. The changes reach from the editor and navigation to the smaller details, including tabs, menus, and dialogs. | ||
|
|
||
| The biggest additions are a built-in query builder, operation collections, and Tree and Table response views. |
There was a problem hiding this comment.
| The biggest additions are a built-in query builder, operation collections, and Tree and Table response views. | |
| The biggest additions are a built-in query builder, operation collections and sharing, fragment extraction, and a table response view. |
|
|
||
| [View the resulting fragment and response as a still image](/img/blog/graphiql-6/09-fragment-extraction-dark.png). | ||
|
|
||
| The builder also provides argument inputs, supports promoting scalar arguments to variables, and offers type selections for fields that return interfaces or unions. |
There was a problem hiding this comment.
Does it fix the long-standing issue with list inputs? If so, that's worth shouting about!
|
|
||
| When provided by the transport, GraphiQL shows the HTTP method, status, elapsed time, and response size of the most recent request in the response header. These details give you more context when inspecting a result, especially when the server returns an error response. | ||
|
|
||
| By default, `createTransport` discovers which HTTP methods your server supports and prefers `QUERY` for queries, followed by `POST` and `GET`. If discovery is unavailable, it falls back to `POST`. Mutations continue to use `POST`. |
There was a problem hiding this comment.
How does discovery work? We've not spec'd QUERY or OPTIONS yet. Is it just issuing e.g. {__typename} and treating non-200 as "not supported"?
Mentioning that GraphiQL 6 supports the latest GraphQL over HTTP spec, including defaulting to the recommended media type (if it does), would be great 👍
|
The videos are really effective at detailing the features; check them out in the preview: |
|
@benjie how did you make the preview work? That is super handy 🙏 |
Description
GraphiQL 6.0.0 is released. This adds the release post covering the redesigned workspace, query builder, collections, response views, and transport API.
Includes screenshots and two captioned videos, with playback controls, posters, and still-image fallbacks. The post is dated November 1 (the release date); the date can be adjusted when scheduling publication.