Nick
07/02/2018, 9:59 AMjbonigomes
07/02/2018, 10:55 AMTanner
07/02/2018, 11:18 AMromshark
07/02/2018, 12:32 PMJenkins
07/02/2018, 12:32 PMzonofthor
07/02/2018, 12:40 PMromshark
07/02/2018, 12:45 PMsenorcodecat
07/02/2018, 2:21 PMjsleeuw
07/02/2018, 2:21 PMsenorcodecat
07/02/2018, 2:21 PMsenorcodecat
07/02/2018, 2:21 PMjsleeuw
07/02/2018, 2:21 PMjsleeuw
07/02/2018, 2:22 PMsenorcodecat
07/02/2018, 2:23 PMjsleeuw
07/02/2018, 2:23 PMjsleeuw
07/02/2018, 2:39 PMjsleeuw
07/02/2018, 2:39 PMsenorcodecat
07/02/2018, 2:40 PMsenorcodecat
07/02/2018, 2:40 PMlewisblackwood
07/02/2018, 3:15 PMfieldOne
, the CLI will show it being successfully added and graphql get-schema --project database
running as a hook. However, the prisma.graphql
file doesn't show the new field and the database isn't updated. If I add another field, e.g. fieldTwo
, and deploy, then fieldOne
is now added and the prisma.graphql
shows it as a field. It's like the deploys are one step behind the changes to my data model. Has anyone seen anything similar?Michael Jones
07/02/2018, 5:37 PMextend
right? It does not seem to be working: # import Query, User from "./generated/prisma.graphql"
type Query {
me: User
}
extend type User {
authToken: String
}
I am unable to return authToken
from a custom resolver like I am expecting.Darryl
07/02/2018, 5:43 PMDarryl
07/02/2018, 5:43 PMNick
07/02/2018, 7:30 PMNick
07/02/2018, 7:31 PMNick
07/02/2018, 7:59 PMnpm i -g prisma
Nick
07/02/2018, 7:59 PMJenkins
07/02/2018, 8:01 PMzak.singh
07/03/2018, 12:58 AMnoahdavis
07/03/2018, 2:00 AM