Github
Joined June 2019
- Tweets183
- Following68
- Followers786
- Likes823
We start with a relatively simple example of JSON5.
Configuring plugins by response content types, we could make handling additional, novel and ad-hoc content types possible, beyond the current spec
1
1
you can add graphiql-explorer to [email protected] now using the new sidebar plugins that use graphiql/react
demo:
graphiql-explorer-thomasheye…
example:
github.com/graphql/graphiql/…
community spec working groups & reference implementation / ecosystem maintainers when the RFC process is fruitful & millions of language users can access new/improved language/protocol features & tooling
youtube.com/watch?v=0hiUuL5u…
1
🐛 ✨ 🦋
the metamorphosis has begun!
deploy-preview-2515--graphiq…
github.com/graphql/graphiql/…
graphql-js weekly download rate keeps growing!
this measure is useful across languages because almost all graphql browser clients use this library
npmtrends.com/graphql
2
Multi-Root workspaces introduce so much complexity in concert with graphql-config multi-project config!
This presents an exciting opportunity to rewrite a big part of the LSP server.
github.com/graphql/graphiql/…
1
Did you know that graphiql has supported auto-filling field leafs since 2017?
With a little config by users, or a better API, this could be the solution to the age-old #graphql unicorn of query { myField{ * } }
You can customise this using a single prop! github.com/graphql/graphiql/…
2
6
@heyenbrock is working on a design preview of the 2.0.0 redesign! And has been making major architectural changes through 1.x minor versions to prepare - with the evolving @graphiql/react sdk as a lovely outcome. Getting so close!
deploy-preview-2483--graphiq…
github.com/graphql/graphiql/…
We have news about GraphiQL 2's design! 🎉
After all the great feedback from the community, we've incorporated changes around theming, usability, and extensibility.
Let us know what you think: github.com/graphql/graphiql/…
@orta and I (rikki) will be merging vscode-graphql into the monorepo to complete the reference ecosystem and save maintainers, contributors & users a bunch of time. it is our ref/testing implementation for the language server! Also merging interface, parser & utils
Thoughts?
ALT A stack diagram of the graphql IDE reference ecosystem in graphql/graphiql monorepo. A legend denotes contrib (purple) and reference (pink) graphql-language-service is depicted in the middle, and above it the language sever, cli and vscode-graphql (reference), as well as sublime, nvim and emacs plugins (contrib) below graphql-language-service is monaco-graphql and codemirror-graphql, which are used to create graphiql@2, graphiql < 2 (reference), as well as graphql playground, altair and insomnia (contrib)
Check out our Github API Explorer Example using Monaco Editor!
monaco-graphql.netlify.app/
@Netlify built-in oauth support made this too easy
1
3
new graphql-playground versions published! 🥳
koa & hapi users now finally have all the latest updates 💪
other middlewares & html/react pkgs have a few important bugfixes
electron build needs love: github.com/prisma-labs/graph…
#GraphQL
