ah gotcha. well you can use our APIs from anywhere with HTTP post requests simple smile

I'm not sure though how well Zapier integrates with this, I haven't used it before. Maybe you can share a bit more about your context

@thisismissem This is definitely something we want to support. I also don't know if Zapier is flexible enough to do this, but please share some feedback once you have tried it out!

You could do a custom zapier integration to post a GraphQL query with a nicer editor, rather than a standard http request style editor

but that'd be how I'd solve the question from @yoamomonstruos

Off topic: Who'll be at the GraphQL meetup tonight?

✋

Looking forward to meet you 🙂

as organizers, pretty much the whole graphcool team simple smile

wooo

I'll say hi; perhaps I can discuss with you something I'm working on

Hey everybody <!here>! @kamil is currently giving a talk which is streamed here: https://facebook.com/GraphcoolHQ/

Anyone using Apollo-graphql know how to have multiple mutations on a single component? Looking for an example.

hey, this might be helpful simple smile https://github.com/learnapollo/pokedex-react/blob/master/exercise-06-solution/src/components/PokemonCard.js#L97-L99

@nilan: yes!

Hi! I've been integrating graphcool with Zeit Next.js, and it worked well so far 🎉 Now I'm reintroducing authentication, and I wonder how to do that with Next's server-side rendering. In the past I simply stored the auth token to localStorage, but there's no access to localStorage as HTTP requests directly go server-side. Help appreciated 😄

Oh wow that's awesome @sdubois! Are you planning to write a blog post about it? This could be super cool for all of our users!

happy to do so when I wrap my head around it 😬 😄

About the serverside-pre-auth: You could use cookies? 😄

OK I don't know anything about cookies, just vaguely remember from a past cybersecurity life it's not the most secure

Yeah, I'd also rather see it as a proof-of-concept

i need to convert the auth token received during auth0 flow to cookie form somehow?

what would be the proper way, instead of cookies?

I think the best would be if you could bake it into a pre-rendered JS context

sorry don't know what you mean

I'm not sure how Next.js works for that. I'd try to build a cookie based solution first to learn how it works and then improve it as a next step once you have a more solid understanding.

OK. Any pointers to learn about cookie based auth? All I know of is the token returned by the

signinUser

mutation, which previously I sent as header

Authorization: Bearer <token>

.

Hmm not really, it's more of a general concept and has nothing to do with how Graphcool works

@sdubois: as a server you can request the browser to store a cookie (key-value) on the user's computer specific to a certain context (usually your domain.) Then you can access the value of the cookie in future requests to the same context. I'm not familiar with next.js at all, but if it handles server requests and manages to get the authentication token, you can store it in the cookie of whoever is requesting your server.

@sam thanks for the explanation, it makes a bit more sense. I just still need to figure out how to assemble the code to do that