rohanray
02/02/2018, 7:54 AMnilan
02/02/2018, 7:56 AMmax
02/02/2018, 10:30 AMrick
02/02/2018, 11:32 AMJosef Henryson
02/02/2018, 11:35 AMMoritz
02/02/2018, 12:27 PMsrc/generated/prisma.ts
with the header text: # THIS FILE HAS BEEN AUTO-GENERATED BY "PRISMA DEPLOY"
# DO NOT EDIT THIS FILE DIRECTLY
However, when I delete the file and redeploy, it does not get regenerated and yarn dev
gives an error complaining that it is not there. This is a problem, since any auto generated files should be regenerated and not statically expected. I ran into this issue when migrating an existing node-prisma app to typescript. Any help?Nikhil
02/02/2018, 12:33 PMPieter
02/02/2018, 1:28 PMpatrick_madx
02/02/2018, 2:06 PMjohhansantana
02/02/2018, 4:14 PMnow
what's my subscription url?Janne
02/02/2018, 4:25 PMKimiiz
02/02/2018, 4:41 PMDylan_b
02/02/2018, 4:51 PMDylan_b
02/02/2018, 4:53 PMDylan_b
02/02/2018, 5:00 PMDylan_b
02/02/2018, 5:02 PMSumant
02/02/2018, 6:43 PMSumant
02/02/2018, 6:45 PMSumant
02/02/2018, 6:49 PMlawjolla
02/02/2018, 7:20 PMWhoops. Looks like an internal server error. Search your cluster logs for request ID: api:api:cjd6bd6mf4yni01724rcl7jm0
for a create mutation on a shared cluster. I take it there's no way to view logs on a shared cluster?dccarmo
02/02/2018, 7:36 PMMr.niko.la
02/02/2018, 8:06 PMMr.niko.la
02/02/2018, 8:07 PMlawjolla
02/02/2018, 8:22 PMPost
type in schema.graphql
that isn't defined in schema.graphql or imported at the top.peter
02/02/2018, 8:30 PMuser
02/02/2018, 8:31 PMhttps://prisma.slack.com/files/U6A7WT4SV/F92H0S6MN/iterm2002.pngā¾
nilan
02/02/2018, 8:31 PMjonoirwinrsa
02/02/2018, 9:44 PM# User can only read projects that belong to the same client or User is Admin
query read($node_id: ID!, $user_id: ID!) {
SomeProjectExists(
filter: {
id: node_id,
client: {
users_some: {
id: $user_id
}
}
})
SomeUserExists(
filter: {
id: $user_id,
userType: Admin
})
}
travis.gregory
02/02/2018, 10:10 PMharrisrobin
02/02/2018, 10:14 PM