GraphQL request authors switch tools to inspect and edit queries
Developers writing and testing GraphQL requests in API clients such as Postman have asked for schema documentation beside their queries, plus better formatting and folding for navigating request bodies. Without those conveniences, they report switching to GraphiQL or GraphQL Playground and copying queries back and forth; some also want shared fragments to reduce duplication. The reports are mostly from 2019–2022, so the current state of these tools needs checking before building.
For developers testing GraphQL APIs in API clients. Mentioned from Aug 2019 to May 2024 on GitHub and Hacker News.
13 different people described this problem in 5 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 5.1/10
- Frequency
- 9.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
I find it significantly more difficult to write GraphQL requests in Postman than other tools because there seems to be no way to look up GraphQL schema documentation from my query code
nickserv on GitHub (postmanlabs/postman-app-support)Jun 2022+56 upvotesAsked for a toolWants to switchI'll generally build my graphql queries in another tool/UI like graphiql for my server, then copy it into postman. If I have to modify it a lot, I'll have to copy it from postman, paste it into another tool, format it, then copy it back into postman
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 4 places to find your first customers
- 11 more quotes from people who have this problem
- Current workarounds, existing solutions and risks