Skip to content
This repository has been archived by the owner on May 26, 2023. It is now read-only.

Expose Extensions in Schema Introspection #6

Open
jasonbahl opened this issue Sep 21, 2017 · 0 comments
Open

Expose Extensions in Schema Introspection #6

jasonbahl opened this issue Sep 21, 2017 · 0 comments

Comments

@jasonbahl
Copy link

For tools like GraphiQL to make use of Extensions, I think there needs to be some Extension introspection of some sort, so that the extensions that exist can be known by tools like GraphiQL.

I envision GraphiQL having some interface, like a Muiti-Select that lets you choose which options you want to include in your request.

But for that to happen, GraphiQL would have to have knowledge of registered extensions, so that it could build out a Select with the options.

This ties in with #5 where a standard for dictating what extensions to include or exclude can be handled in the request in some fashion. (of course, server side rules could be configured to have certain extensions always on or always off, regardless of the client's request)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant