Thanks @artyom 👋 back. Looking forward to this service for sure.

@zmarkan hello! welcome! graphcool

Hello! 🙂

it’s a proper party in the graphcool slack today 🦜 🎉 hi, @jonathan & @roth

Hello guys

Hello. I’ve been thinking about releasing the app im writing as opensource. Not that it would be usable by anyone but maybe someone can learn something. Is there a way to export my graph.cool schema into something I can use with graphql-up? would be awesome to have that with the readme..

Is the roadmap being kept up to date? https://github.com/graphcool/feature-requests/projects/1

gettin an odd permission error - when I register a new user using an auth0 id token, I get an apollo permission error, but when I look at graphcool, I see the user was created in the database

GraphQL error: Insufficient Permissions
    at new ApolloError (apollo.umd.js:1490)
    at apollo.umd.js:2107
    at tryCallOne (core.js:37)
    at core.js:123
    at JSTimers.js:100
    at Object.callTimer (JSTimersExecution.js:95)
    at Object.callImmediatesPass (JSTimersExecution.js:199)
    at Object.callImmediates (JSTimersExecution.js:214)
    at MessageQueue.js:214
    at guard (MessageQueue.js:46)

anyone have suggestions on how I could debug that?

does apollo behind the scenes try to fetch the created user record right away to refresh its cache or something? Or does it have something to do with how I set some private fields in the graphcool permissions?

@katsikas hi there! 👋

hi @levente.dominguez nice to have you join us! graphcool

ahoi @ferdi 👋 graphcool

Hi there 👋

graphcool looks great. I will give it a spin.

@griffinsockwell hi!

hey @hmeissner 🙌

Is there a rough ETA for more advanced permission settings? I only see “Query permissions”

Note: this feature will roll out in the future.

in the docs. I’m looking for a way to work with multiple user roles.

Unable to find any info in the

docs

on email authentication using

react-native

. Any pointers?

I just got an error from graphcool

[ { message: 'Whoops. Looks like an internal server error. Please contact us in Slack (<https://slack.graph.cool>) and send us your Request ID: cj0evqplp46n30168jzob6ass',
       requestId: 'cj0evqplp46n30168jzob6ass',
       path: [Object],
       locations: [Object] } ] }

I couldn't get a nested mutation using variables working

I used this article as a guide https://www.graph.cool/blog/improving-dx-with-nested-mutations-vietahx7ih/

but I kept getting an error similar to the one that I pasted above

Is there a recommended way to do server side rendering with Graphcool?

@noktasizvirgul @do4gr @paulo @zirho6 @samtoday hello from the graphcool team! ping us with questions, if anything comes up

Hello! I’m using Graph.cool with Auth0, and I was wondering what the correct login flow is when I have the token

I can run a

createUser

mutation, but it errors the second time they log in as the user already exists

Is there a way to create a user if it does not already exist?

Otherwise do nothing

Hi @lpil - When the user already exists you can simply use the id_token returned by auth0 as the authorization token you include in requests to Graphcool. Most apps create separate flows for signup and signin, so in that case you already know if you need to call the createUser mutation. If you have a combined flow I would suggest to always call createUser and simply catch the error.