graphiql icon indicating copy to clipboard operation
graphiql copied to clipboard

GraphiQL & the GraphQL LSP Reference Ecosystem for building browser & IDE tools.

Results 391 graphiql issues
Sort by recently updated
recently updated
newest added

This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically....

a starting point, based on https://github.com/graphql/vscode-graphql TODO: - [x] as with `vscode-graphql`, port to the latest `vscode-anguageserver-client` using `vscode-anguageserver-client/node` import - [x] fix embarassing package.json typos haha - [ ]...

enhancement
vscode-graphql

This adds some more documentation in the simplest form possible: JSDoc comments :D Those should also be picked up by typedoc and enhance the docs we generate and push to...

My VSCode plugin is failing to start, logging the following error: ![image](https://user-images.githubusercontent.com/13839490/182178999-081eb51a-7855-4467-9356-0bdd590b8a58.png) ``` 8/1/2022, 11:58:03 AM [1] (pid: 32510) graphql-language-service-usage-logs: WARNING: graphql-config error, only highlighting is enabled: this.splice is not...

lsp-server

Some keydown events seem to bubble up too far. One particular example is the docs search combobox. When pressing escape, the event bubbles up all the way. When rendering GraphiQL...

@graphiql/react

I'm noticing @divyenduz 's original `vscode-graphql` package.json had pinned `dependencies` and I think I understand why. ^ versions when you're shipping shared libraries work pretty great. But for end consuming...

housekeeping
vscode-graphql

When editing type system definitions, the autocomplete suggestions aren't super helpful (and kinda hard not to accidentally trigger at the top-level of the document): In this PR I've updated one...

enhancement
language-interface
monaco-graphql

Extracted the logic that creating diagnostics to a method.

lsp-server

If you construct a `GraphiQL` instance with a bad fetcher `fetchError` gets persisted in `SchemaContextType` forever. You can still fetch a new schema but the `DocExplorer` will always show "Error...

More cleanup for v2: This PR adds a `GraphiQLProvider` component that renders all the providers from `@graphiql/react`. I also deduplicated the prop definitions and moved them to where they originate....