Introducing GraphQL Support for Insomnia | Hacker News Reader

Introducing GraphQL Support for Insomnia

insomnia.rest

84 pointsthejosh26 comments

I'm the creator of Insomnia and I'd love to hear your feedback if you try it out! I'm still a novice to GraphQL, so I'd like to make sure that it accommodates all use cases.

~ Gregory

Cool. Insomnia is quite good. I prefer it over Paw (for MacOS only) because it is cross platform and I only want to learn one tool that works on both Mac and Linux.

Thanks for all the hard work!

Glad to hear it. Thanks for the kind words!

I've been using Insomia for a while, and really, really like it (hence why I submitted this post here :D).

The GraphQL support looks good, and will try it out with our backend.

Awesome, thanks for posting :)

Be sure to submit any issues you may have via Slack/GitHub/Email

I think as long as it's good or better than GraphIQL, you've got an advantage.

Timely update as I am learning GraphQL with it and it is simpler now to define the request body.

Great work and keep it up.

Nice! That's exactly why I implemented it (I just learned it too for a side project)

Hey simple question: mobile now... does this support sending auth headers per request?

Yep!

Just tried it. I LOVE IT! Great work!

Gregory, thanks for introducing Insomnia to the world and thanks for continuing to make it better!

What's the difference between using this and using graphiql?

Lots, actually. Since Insomnia is a full-featured HTTP testing tool, you can use all other Insomnia features with GraphQL like setting custom headers, filtering responses with JSONPath, Nunjucks templating, etc.

What a clever domain name.

Thanks!

This is fantastic news as I loved your tool, but it fell out of favor as I startee using graphQL more.

Definitely looking forward to ditching graphiQL!

Does it support imports for graph. cool?

I haven't used graph.cool yet but as far as I can tell it's just another GraphQL backend so yes, it should work just the same.

I'm curious as to why you want to ditch graphiQL. I find graphiQL to be one of the best things about the GraphQL ecosystem.

Purely aesthetics. I'm a weirdo, but a pretty UI really enhances my development experience. I'll use a less functional product if it pleases my pupils, like Hyper over iTerm2. (Not saying insomnia is less functional, it's just very pretty :)

Perhaps I'm missing it, but it appears this only works with POST requests?

You are probably correct. The server-side GQL implementations I have worked on expect only POST requests, and expect each requests' body to contain a query or a mutation.

Good point, looks like my implementation of GraphQL was't correct. Thanks!

GraphQL actually does support GET requests, but most clients (like Apollo) don't support it out of the box.

http://graphql.org/learn/serving-over-http/

That's what I had though, was just surprised by the lack of client support.

Reply on news.ycombinator.com