-
Notifications
You must be signed in to change notification settings - Fork 856
Closed
Labels
featureproduct/api-designprotocol/graphqlIssues relating to the GraphQL protocol within PostmanIssues relating to the GraphQL protocol within Postman
Description
After the kind comment here and the thread being locked, I've decided to open this issue as I know other people is waiting for proper GraphQL support like myself.
Is your feature request related to a problem? Please describe.
- The current GraphQL support rely on people having to describe the schema on the API tabs but doesn't allow people to import the schema using the introspection endpoint, which is how everyone else does the schema import on their tools as the introspection endpoint was designed for that.
- The auto-complete/intellisense on the request using that "imported" schema, expect people to know before hand the fields or to be reading the schema elsewhere which beats the purpose of import the schema.
Describe the solution you'd like
- On the API tab, when adding a new API, click on "Add schema" would give you an option "Import from URL" which would take an endpoint URL to GraphQL so introspection can be used. In fact, it could expect any OpenAPI schema as well, but that is for another feature request.
- Whenever I press ctr/cmd+space, we want the list of fields for that given context. Just like any other tools have.
Additional context
Check how Insomnia, GraphiQL or GraphQL Playground. They are enough to make postman customers happy. Simple and direct to the point.
bastos71, samkit-jain, ndrsllwngr, tomashanacek, samueldfo and 289 moreebonertz, lauraluiz, ruaridhnewman, SciGno, Bwvolleyball and 82 morezolotokrylin, LucasLopesr, alikadir, shirshak55, ild0tt0re and 50 more
Metadata
Metadata
Assignees
Labels
featureproduct/api-designprotocol/graphqlIssues relating to the GraphQL protocol within PostmanIssues relating to the GraphQL protocol within Postman