rafal
08/20/2017, 1:03 PMwilson29thid
08/20/2017, 2:32 PMmikedklein
08/20/2017, 4:02 PMmikedklein
08/20/2017, 4:18 PMjvbianchi
08/20/2017, 5:15 PMsubscriptions-transport-ws
? Can I use middleware?jvbianchi
08/20/2017, 5:29 PMkai
08/20/2017, 6:04 PMDaniel K.
08/20/2017, 6:24 PMDaniel K.
08/20/2017, 6:25 PMStefan
08/20/2017, 9:00 PMdixonbydesign
08/21/2017, 2:48 AMError: GraphQL error: None of the following arguments provided: List(auth0UserId, id)
) seems to imply that I should be passing an auth token with the query. But the auth token is already being set as a header with every request. I also don't see the token being passed in the userQuery
in this example: https://github.com/graphcool-examples/react-graphql/blob/master/authentication-with-auth0-and-apollo/src/components/CreateUser.jsdixonbydesign
08/21/2017, 2:49 AMdixonbydesign
08/21/2017, 3:30 AMuserQuery
. Here is how I ended up writing my query:
const userQuery = gql`
query getUser($auth0UserId: String) {
User(auth0UserId: $auth0UserId) {
id
name
emailAddress
}
}
`;
scott_moss
08/21/2017, 5:35 AMgreatscot
08/21/2017, 7:10 AM@isunique
. There must be a better way - would be interested to know how for future.yakupad
08/21/2017, 8:17 AMkumorig
08/21/2017, 9:41 AMdtuite
08/21/2017, 10:13 AMArticle
model. I’ve released v1 of the app which orders articles based on their `createdAt`datetime. Now I want to release a new version, v2, which adds a publishedAt
field to Article
and uses that to order posts in the UI.
First I add the field to my schema and write a script to migrate my data so that all existing articles have their publishedAt
value set to that of the createdAt
value. Now I can release v2 of my app which displays articles based on publishedAt
.
The problem is that users on v1 of the app are still creating new articles which don’t have a publishedAt
value. I can’t force them to upgrade and I can’t migrate the data on it’s way into Graphcool with a serverless function because I can’t add new fields to an incoming payload. As far as I can see I’m basically stuck running my original data migration script over and over until all legacy users have migrated.
Is there a better way?sigo
08/21/2017, 11:05 AMsigo
08/21/2017, 11:23 AMyakupad
08/21/2017, 11:54 AMyakupad
08/21/2017, 12:28 PMuser
08/21/2017, 12:30 PMhttps://prisma.slack.com/files/U6EBQ5Z5F/F6S7SSJS2/ekran_resmi_2017-08-21_15.24.41.png▾
user
08/21/2017, 12:31 PMhttps://prisma.slack.com/files/U6EBQ5Z5F/F6S7SSJS2/ekran_resmi_2017-08-21_15.24.41.png▾
user
08/21/2017, 12:36 PMhttps://prisma.slack.com/files/U6EBQ5Z5F/F6S7SSJS2/ekran_resmi_2017-08-21_15.24.41.png▾
user
08/21/2017, 12:37 PMhttps://prisma.slack.com/files/U6EBQ5Z5F/F6S7SSJS2/ekran_resmi_2017-08-21_15.24.41.png▾
user
08/21/2017, 12:38 PMhttps://prisma.slack.com/files/U6EBQ5Z5F/F6S7SSJS2/ekran_resmi_2017-08-21_15.24.41.png▾
user
08/21/2017, 12:38 PMhttps://prisma.slack.com/files/U6EBQ5Z5F/F6S7SSJS2/ekran_resmi_2017-08-21_15.24.41.png▾
user
08/21/2017, 12:38 PMhttps://prisma.slack.com/files/U6EBQ5Z5F/F6S7SSJS2/ekran_resmi_2017-08-21_15.24.41.png▾
user
08/21/2017, 12:39 PMhttps://prisma.slack.com/files/U6EBQ5Z5F/F6S7SSJS2/ekran_resmi_2017-08-21_15.24.41.png▾