graphiql
graphiql copied to clipboard
graphql
Proposal: GraphQL Voyager plugin
this is something @IvanGoncharov himself (one of the original voyager authors) proposed and is looking forward to! I'll let you know when the plugin proposal template is ready, busy with the plugin API proposal itself right now!
@acao Not sure that foundation should host plugins that wrap 3rd-party libraries/tools. I think it should be hosted by projects themselves or by the community on external repos.
makes a lot of sense! i think we can host these discussions here for third party modules as a way to capture interest, since this is frequently requested, but most of the actual plugin proposals people are about to be making will be built/maintained elsewhere. does that make sense? even for third party plugins, best to keep all the proposals under one roof for now.
@acao Totally fine with proposals 👍 and thinking it's an excellent repo to collect them and think about them as use cases to design plugin API.
Here's the current GraphiQL structure:
So the plug-ins can only use the left side of GraphiQL?
Here's the GraphQL Voyager UI:
Is it possible to create plug-ins that (also) use the right side of GraphiQL?
As an idea, the GraphQL Voyager plug-in for GraphiQL could use the left side for docs (e.g. built-in GraphiQL Docs) and the right side for graph visualization.
If the user clicks on a type/field on the left side, the visualization focuses on that type/field, and vice versa.
Is it possible to create plug-ins that (also) use the right side of GraphiQL?
With the current plugin API this is not possible. However, you can render anything you want in the plugin component, for example you could add a "full-screen dialog" which would give you the most amount of screen possible which might make sense for this kind of plugin.
Also note that the plugin pane can be resized to take up the full width of the page:
