🎡  GraphQL developer portal featuring an IDE (Apollo Explorer), auto-documentation, metrics reporting, and more. This repo is for issues, feature requests, and preview docs. 📬
Namespaces as presented in Apollo Studio are not obvious and require foreknowledge making them easy to miss when exploring an API.
By way of example, in the public apollo-platform GraphQL the graph Field is how a Namespace is exposed, hiding goodies like upsertContractVariant, publisSubgraphs etc.
What type of feedback is this?
[ ] Question
[ ] Idea
[ ] Bug
[ ] New example or operation collection
[x] Feedback
Is there anything else you'd like to share about the Platform API?
It would be good to separate Namespaces from Fields to help developers explore API's
Context
Namespaces as presented in Apollo Studio are not obvious and require foreknowledge making them easy to miss when exploring an API.
By way of example, in the public
apollo-platformGraphQL thegraphField is how a Namespace is exposed, hiding goodies likeupsertContractVariant,publisSubgraphsetc.What type of feedback is this?
Is there anything else you'd like to share about the Platform API?
It would be good to separate Namespaces from Fields to help developers explore API's