It's much easier to understand and utilize data when you are presented it visually, which is what the explorer aims to achieve. (I've never seen a graphiql page implemented without this feature before because it's so critical to how people typically create gql queries).
Without it, you have to refer to the docs section and manually copy over the schema you need, a process substantially simplified with the explorer.
Screenshot or video of the issue (if applicable):
Here's an example of this in another (competing) service, compared to how it appears in prismic. You can immediately see the benefit of just knowing what data you have to work with.
Hello Dan, welcome to the community, and thanks for reaching out about this!
This is something we've talked about in the past and we're already tracking it in our backlog. But I'll add your post as part of the open feature request.
Thank you for the feedback
1 Like
Pau
closed , flag & select 'Something Else' to reopen.
4
Hey @Pau, is it mapped for the near future? It is a major blocking factor for better adoption here. Other tools are using it and it helps to reduce the time for developers to elaborate queries. Check GraphCMS, Hasura, or even WordPress WP GraphQL plugin, all using the same explorer.
button to show your support for the feature and check out our