gildas
06/18/2017, 9:19 AMdanielvdm
06/18/2017, 9:44 AMdanielvdm
06/18/2017, 9:44 AMgildas
06/18/2017, 9:56 AMbartamon
06/18/2017, 11:16 AMjaga_santagostino
06/18/2017, 12:09 PMbe4r
06/18/2017, 5:11 PMgeekodour
06/18/2017, 5:29 PMthis.props.data.loading
does not work sometimes. This has to do something with the graphcool servergeekodour
06/18/2017, 5:29 PMgeekodour
06/18/2017, 5:30 PMgeekodour
06/18/2017, 6:03 PMbe4r
06/18/2017, 6:14 PMconst createUser = gql`
mutation ($idToken: String!, $name: String!, $emailAddress: String!){
createUser(authProvider: {auth0: {idToken: $idToken}}, name: $name, emailAddress: $emailAddress) {
id
name
createCloset(userId: id)
}
}
`
is this the right way? How can i pass in the createdUser's id into createCloset?peterp
06/18/2017, 7:00 PMckelley
06/18/2017, 7:47 PMcreatedAt
. The main way I can think to do this is by using a through type that manually merges the two. Is there a better option, and if not, what are the performance implications of using that strategy?s0enke
06/18/2017, 7:49 PMtomhut
06/18/2017, 7:52 PMagartha
06/18/2017, 9:15 PMmonte9
06/18/2017, 9:51 PMckelley
06/18/2017, 10:09 PMcreatedAt
field be overriden?trond
06/18/2017, 11:38 PMtrond
06/19/2017, 12:03 AMckelley
06/19/2017, 12:04 AMcreateUser
mutation only in your own applications?
2) Securely storing JWTs on the client side (both on a mobile device and the web)
3) Invalidating user tokens if necessary?trond
06/19/2017, 12:11 AMagartha
06/19/2017, 12:20 AMvisualbbasic
06/19/2017, 1:58 AMvisualbbasic
06/19/2017, 1:58 AMvisualbbasic
06/19/2017, 1:58 AMBarrie
06/19/2017, 5:06 AMmentallyretired
06/19/2017, 5:15 AMmentallyretired
06/19/2017, 5:16 AM