Hi Emil 🙂 The signinUser mutation looks like this:

mutation{
  signinUser(email:{email: "", password:""}){
    token
  }
}

Hi Søren, 🙂 Yes, but if i’m using auth0 i need to send the token instead right ?

That’s correct. Then it would look like this:

mutation{
  signinUser(auth0:{idToken:""}){
    token
  }
}

Alright, i made some logic for choosing the correct template for the mutation, but it’s quite complicated compared to createUser where its

$authProvider: AuthProviderSignupData!

But thank you Søren, ill try it out 🙂

Awesome i got it working, i’m not so used to making this login logic, but I have created a user with the same email as i’m using for google, but after creation i now have 2 users in the User.table, so i want to hear if there’s any tricks on merging multiple user into one in graph.cool ? So the user can login with multiple sources but still be the same?

This is a complicated topic in general and Graphcool does not currently have a built in solution to this. One option is to let users link their accounts after they are created. For example you could have a button on the user profile page to link with other account. At my previous company we didn’t handle this until 3 years after launch when we had a team of 15 engineers. So my suggestion is to focus on what makes your product awesome instead of tedious user management 🙂

Haha, i guess thats why it wasn’t so obvious for me how to handle this. Because if you are not handling this logic i can only see the possibility of linking them together in settings, but then i would need to do a check if the auth0 email is already registered in backend, and then ask them to sign in with previously created user, and then go link the accounts. And thats a whole story by itself! So thank you for your suggestion, ill focus on that later on when i have a rocking app and about to board real users 🙂

I’m happy for now with having email and auth0 login signing in if user is already created, thanks for the tip in your docs 😉

Your welcome 🙂

very slick onboarding process! I enjoyed going through it

having the downloaded app already configured for my graphcool endpoint was a very nice touch

Agreed. Excellent onboarding. Anyone here ever used graphql with backbone?

Hey guys! Hi everybody! How to fix this issue ERROR in [default] File '.../modules/$.js' has unsupported extension. The only supported extensions are '.ts', '.tsx', '.d.ts'.?

Thanks @andy & @paulfalgout! Glad you like it! Is there anything what could have been easier?

@paulfalgout a few people did I think, but most are using React or Angular when building web apps.

Hey @denis. Which example are you referring to?

Does anyone know how to get up to speed with what happened at the GraphQL summit, e.g Relay 2 features and release schedule, Apollo, GatsbyJS, etc?

@sdubois The website states that “We'll be posting all session recordings and available slide-decks here shortly!” Maybe @sashko can provide some insight on the timeframe 🙂

great thanks @sorenbs, will wait simple smile

When are you guys planing on going out of beta? 🙂

Hey @sschonert! Early next year. 🙂

Hey there schickling - cool! i’m not all that firm on backend, and im considering outsourcing it. Where are you guys located?

Sounds like a great fit! We have multiple server locations. The nearest one for you would be in Ireland.

Yea i think so too - you guys have managede to create a nice open feel to the whole project, which not only appeals to me but for some reason engages me. But for me to consider this i’d need the ability to validate user input and process the model before sending it back. Any plans on the last part?

@schickling ^ (not to be pushy, just assuming your not constantly checking for new messages 🤓)

Oh wow, thanks a lot for your great feedback. That's exactly what we're going for! Very good point aswell, @sschonert! We indeed have this feature on our roadmap for December: https://github.com/graphcool/feature-requests

@schickling you are more then welcome. 🎉 I’m aware of the roadmap, just cant seem to spot to feature that allows me to process data before sending it back to the user. Like weighing the results after custom scores

This should be a first step in this direction

Custom mutations are also planned