Before GraphQL, Paw was a necessary and often daily part of my FE team’s toolset. Since GraphQL and tools like Graphiql, I haven’t found myself using Paw. Its killer-feature for me was chaining together long sequences of REST requests that dynamically depended upon one another’s results.
I’m curious if others are using Paw in a GraphQL context?
I use Paw for GraphQL every day, including variables, schemas, and docs. The autocomplete works well enough, and when plugging into the larger Paw project things work very well.
My only big gripe is I can't write JSON to modify variables, I have to interact with a JSON tree UI and add items one at a time.
3.2 added some rudimentary GraphQL support but it’s not comparable to Insomnia so I went back to that
Just loading it now and there’s an update (3.2.1) - it mentions some GQL documentation improvements in the change log but unsure if it’s tangibly better
The GQL features have nothing on GraphiQL+Explorer. Depending on how much you value the native UI, dynamic features etc it may still be worth it. It is for me, but I use it alongside GraphiQL all the time.
Before GraphQL, Paw was a necessary and often daily part of my FE team’s toolset. Since GraphQL and tools like Graphiql, I haven’t found myself using Paw. Its killer-feature for me was chaining together long sequences of REST requests that dynamically depended upon one another’s results.
I’m curious if others are using Paw in a GraphQL context?