Introducing GraphQL Support for Insomnia(insomnia.rest)

84 ポイント投稿者 thejosh9 年前26 コメント

Introducing GraphQL Support for Insomnia

https://insomnia.rest/blog/introducing-graphql

26 コメント

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

thejosh9 年前

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.

gschier9 年前

Awesome, thanks for posting :)

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

kevinSuttle9 年前

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

tbrock9 年前

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!

gschier9 年前

Glad to hear it. Thanks for the kind words!

dfischer9 年前

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

gschier9 年前

Yep!

dfischer9 年前

Just tried it. I LOVE IT! Great work!

mp019 年前

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

gschier9 年前

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.

max23_9 年前

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.

gschier9 年前

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

johnhenry9 年前

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

gschier9 年前

kevinSuttle9 年前

What a clever domain name.

gschier9 年前

Thanks!

FullMtlAlcoholc9 年前

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?

hn_throwaway_999 年前

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.

FullMtlAlcoholc9 年前

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 :)

gschier9 年前

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.

baconomatic9 年前

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

tylerpachal9 年前

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.

baconomatic9 年前

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

gschier9 年前

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/

baconomatic9 年前

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