veksen
06/14/2018, 5:10 PMveksen
06/14/2018, 5:35 PMveksen
06/14/2018, 5:36 PMendpoint: ${env:PRISMA_ENDPOINT}
secret: ${env:PRISMA_MANAGEMENT_API_SECRET}
datamodel: datamodel.graphql
hooks:
post-deploy:
- graphql get-schema --project prisma
- graphql prepare
Jscott388
06/14/2018, 6:06 PMHenrik Joreteg
06/14/2018, 6:42 PMHenrik Joreteg
06/14/2018, 6:44 PMHenrik Joreteg
06/14/2018, 6:44 PMryannealmes
06/14/2018, 6:56 PMalec
06/14/2018, 7:44 PMryannealmes
06/14/2018, 8:16 PM# import User from "./generated/prisma.graphql"
# import Team from "./generated/prisma.graphql"
type Mutation {
login(email: String!, password: String!): String
signup(email: String!, password: String!, name: String!, username: String!): String
updateUser(data: UserUpdateInput!, where: UserWhereUniqueInput!): User #not sure how to add this ...
}
type Query {
me: User
users: [User!]!
teams: [Team!]!
}
dreadjr
06/14/2018, 8:29 PMgraphql-yoga
and apollo-engine
with tracing enabled. Is there a way to use the traceId or requestId
in a resolver, so i can pass it downstream to another resource?veksen
06/14/2018, 10:34 PMuser
06/14/2018, 11:07 PMnilan
06/15/2018, 12:10 AMveksen
06/15/2018, 12:12 AMuser
06/15/2018, 1:06 AMJonathan
06/15/2018, 1:21 AMDukuo
06/15/2018, 2:49 AMTaylor
06/15/2018, 3:25 AMeugenistoc
06/15/2018, 5:47 AMBrendan Neufeld
06/15/2018, 6:51 AMZLASH
06/15/2018, 9:27 AMwoss
06/15/2018, 10:38 AMprisma deploy
🙂pettanko
06/15/2018, 10:49 AMfredelf
06/15/2018, 1:17 PMprolink007
06/15/2018, 1:50 PMprolink007
06/15/2018, 2:03 PMjhony0311
06/15/2018, 2:17 PMprisma deploy
I get the following error Could not connect to server at <http://localhost:4466>. Please check if your server is running.
Any clue on what is needed to have that working?Jonathan
06/15/2018, 5:41 PMJonathan
06/15/2018, 5:51 PM