cookie support about graphql-request

[mwld]

Your problem might be caused by not including credentials: same-origin in your request header (JakeChampion/fetch#386).

This should now be possible with the release of 1.3.2: #9

Like:

new GraphQLClient(YOUR_ENDPOINT_URL, {
    credentials: "same-origin",
});

[DxCx]

hey @mwld is that actually working for you?
from what i've found isomrophic-fetch will just ignore cookies (or set-cookie header)
i had to write temporary wrapper to support cookies.. :\

[mwld]

Yes this is working for me :)

[DxCx]

yeah well i forgot to mention that i'm using the library from node and not browser.

[DxCx]

You made me dig again with your replay.
i was able to replace my ugly big wrapper with just this line:

global['fetch'] = require('fetch-cookie/node-fetch')(require('node-fetch'))

Now graphql-request just works for node as well.
@schickling i think this is worth mentioning in README.MD
would you like me to open a PR?

NOTE: this won't solve per client cookie, since fetch is global.
if we want to support per GraphQLClient cookie we will need to be able to inject fetch function on client constructor. then we can pass different fetch for each client.

[schickling]

Thanks a lot for bringing this up @DxCx! It would be great if you could mention it briefly in the readme.

Regarding injecting fetch: Let's keep this issue open to see whether other people also have this problem before we're changing the API. @DxCx can you close this issue and create a new one with this concrete suggestion?

[DxCx]

the injection is optional, which means, if no fetch is given in option, it will use fetch as it uses it today. but great! i'll update the README