nordsimon

Yes it might not work with current api but i was planning to add it as an optional thing in the transitionmanager. It is already callback based so it might...

Hi! This library is a very simple wrapper around fetch and doesn’t support subscriptions at the moment. The problem with subscriptions is that they could be transferred multiple way, and...

Nice. I'll take a look at it and get back to you soon

Hm, what happend with the error handling part after query result. When a query returns with errors i wanted it to throw to the catch block so the promise chain...

I'll take a look at this. A bit curious if I should support this with another api

I thought it through and i would like to implement something like this instead Initialize the client ``` javascript var client = require('graphql-client')({ url: 'http://your-host/graphql', headers: { Authentication: 'Bearer '...

Yeah, I do aswell. I tried to support both ways but it became a mess. Maybe adding it to the client would help. But then it won't get connected to...

Okey, so this is where i am now. I added a third argument to the query method which will send the req and res object. I also changed the error...

Since every query has their own req and res i don't want to add it to the client init

Hm, i see. Maybe i can make the headers argument optionally take a function, so in this way you could write something like ``` var client = require('graphql-client')({ url: 'http://your-host/graphql',...