You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is often very helpful to have an endpoint which returns the whole Schema as printed SDL.
This is in some way similar to the build-in Introspection, but "made for humans" and also the SDL is more rich than Introspection as it can contain comments and directives.
The text was updated successfully, but these errors were encountered:
Do you think this should be bound to the graphql endpoint itself directly?
Or should this be more like of a tooling-related, opt-in endpoint and maybe we should expose that as an actuator endpoint?
I am not sure about the differences here, but it should be opt in, yes.
The default path should be probably something like /graphql/schema and return text for a GET.
It is often very helpful to have an endpoint which returns the whole Schema as printed SDL.
This is in some way similar to the build-in Introspection, but "made for humans" and also the SDL is more rich than Introspection as it can contain comments and directives.
The text was updated successfully, but these errors were encountered: