graphiql
graphiql copied to clipboard
GraphiQL & the GraphQL LSP Reference Ecosystem for building browser & IDE tools.
Dear developers, I'm writing this issue because I am a blind developer. So I have to run a screen reader to use my computer. I've found GraphQL very useful for...
For `monaco-graphql` examples, the webworker setup should be very simple, almost a non-issue The vite example with the monaco-editor-vite-plugin shows us how lean it can be. So as should follow...
These are widely useful utilities that are already used by many projects, so we will need to alias them as exports for `graphiql` package until 2.0 at least. We should...
migrate all asynciterable fetching/executor logic possible to utility functions that can be used by `graphiql@1` for now and soon `graphiql@2` it's possible that these would make more sense as `@graphiql/react`...
I find myself testing various queries a lot, and when I do this, it'd be really nice if I could just comment out some query variables (preferably with `cmd +...
Is there a documentation how we can integrate `GraphiQL` in our existing markdown-based documentation? We`d like to have something like [this](https://github.com/graphql/graphql.github.io/blob/source/src/content/learn/Learn-Queries.md): ``` # { "graphiql": true } { hero {...
Probably a low-priority item (wishlist even), but a dark UI theme has been requested - I'm documenting as an issue here.
Migrate just the "classic" DocExplorer set of components over to @graphiql/react, or to a seperate package entirely, such as @graphiql/doc-explorer. A good chunk of important, spec-dependent functionality lives here. we...
A user [reported a UI bug](https://github.com/jonathanawesome/graphiql-prototype/issues/63) in the GraphiQL design prototype I've been working on that's related to `monaco-graphql`. When the model value consists only of comment lines, we get...
## Actual Behavior The extension crashes at startup with this error in GraphQL Language Service output: ```UnhandledPromiseRejectionWarning: Error: Field "TypeWithDuplicatedField.duplicatedField" can only be defined once.``` ## Expected Behavior An error...