Plug-ins APIs

[FluorescentHallucinogen]

Here's the current GraphiQL structure:

1. Is it possible to create plug-ins that (also) use/replace, e.g. one or more panes on the right side of GraphiQL, not only the left pane? E.g.:

Use cases:

• GraphQL Voyager plug-in (see Proposal: GraphQL Voyager plugin #1533)
• using GraphiQL Explorer instead of JSON for variables (see Ideas for improving the Developer Experience and Feature Discoverability OneGraph/graphiql-explorer#10 (comment))
• using data table instead of JSON for response (see Ideas for improving the Developer Experience and Feature Discoverability OneGraph/graphiql-explorer#10 (comment))
• etc.

2. What about (deep) integration between GraphiQL plug-ins?

Use cases:

• Clicking on a specific type/field in the GraphiQL Docs would focus that field in the GraphiQL Voyager, and vice versa
• Ctrl+Click on a specific field in the GraphiQL Explorer would open that field in the GraphiQL Docs (see Ideas for improving the Developer Experience and Feature Discoverability OneGraph/graphiql-explorer#10 (comment))
• Clicking on a specific field in the GraphiQL Explorer would focus that field in the code pane, and vice versa (see Ideas for improving the Developer Experience and Feature Discoverability OneGraph/graphiql-explorer#10 (comment))
• etc.

[FluorescentHallucinogen]

@acao @thomasheyenbrock @timsuchanek cc.

[thomasheyenbrock]

See also #1533 (comment)

There are plenty of use-cases that go beyond GraphiQL, which is just the reference implementation for a GraphQL IDE. We provide all its building blocks with the @graphiql/react package, that would allow you to create your own IDE that implements any of the customizations you linked to here.

That said, my personal take on this is that some of these ideas go beyond what we should build into GraphiQL. They would significantly increase complexity of both code and UI and might only serve a subset of its users that require these specific plugins and functionalities.