Steven Vachon
06/03/2019, 4:15 PMtype Thing {
id: ID! @id
value: String
}
curl -X POST -H "Content-Type: application/json" --data '{ "query": "{ thing { value } }" }' <http://localhost:4466>
Field 'thing' argument 'where' of type 'ThingWhereUniqueInput!' is required but not provided.
koia
06/03/2019, 5:54 PMkoia
06/03/2019, 5:58 PMkoia
06/03/2019, 5:58 PMkoia
06/03/2019, 6:01 PMTravis
06/03/2019, 6:58 PMschrepfler
06/04/2019, 12:28 AMtanuj doshi
06/04/2019, 10:26 AMtanuj doshi
06/04/2019, 10:26 AMtanuj doshi
06/04/2019, 10:26 AMtanuj doshi
06/04/2019, 10:29 AMtanuj doshi
06/04/2019, 10:29 AMPS C:\Users\DHRUMIT\Desktop\mysql-node\helloworld> prisma deploy
Creating stage aada for service aada √
Deploying service `aada` to stage `aada` to server `default` !
! 'ECONNREFUSED': request to <http://192.168.99.100:4466/management> failed, reason: connect ECONNREFUSED 192.168.99.100:4466
Get in touch if you need help: <https://www.prisma.io/forum/>
To get more detailed output, run $ export DEBUG="*"
tanuj doshi
06/04/2019, 10:33 AMAndre Coetzee
06/04/2019, 11:35 AMAndre Coetzee
06/04/2019, 11:37 AMClément Fassot
06/04/2019, 12:00 PM@query('HR Management') @mutation('Management')
). A developer would then just need to produce a datamodel for prisma with the right directives. At first we thought about doing a gateway that stitches a list of schemas automatically, but with recent announces of Apollo federation/gateway and the fact that prisma will soon no longer need a prisma server to do its magic we're forced to reassess things.
I think we could deploy an apollo federation service for each "backend" we provide, this service uses the datamodel of prisma as its graphql schema. Problem is we need to generate the resolvers, or have the developer write them (would be very easy but quite long sometimes). Or we could do a CLI that generates them using the datamodel and prisma client.
What do you guys think ? Have anyone of you been in this situation before where you want to generate resolvers automatically based on a datamodel ?yolen
06/04/2019, 12:09 PMlkbr
06/04/2019, 12:10 PMdpetrick
06/04/2019, 12:11 PMMichał Chmura
06/04/2019, 12:13 PMKimble
06/04/2019, 12:29 PMjoar
06/04/2019, 12:36 PMKimble
06/04/2019, 12:50 PMKimble
06/04/2019, 12:52 PMKimble
06/04/2019, 12:54 PMrpeterson
06/04/2019, 1:22 PMCsaba Tamas
06/04/2019, 1:34 PMHoang
06/04/2019, 1:57 PM(node:5226) UnhandledPromiseRejectionWarning: Error: Project not found: 'default$default'
at BatchedGraphQLClient.<anonymous> (/Users/pham/dev/adviqo/calling-service/node_modules/http-link-dataloader/dist/src/BatchedGraphQLClient.js:69:35)
at step (/Users/pham/dev/adviqo/calling-service/node_modules/http-link-dataloader/dist/src/BatchedGraphQLClient.js:40:23)
at Object.next (/Users/pham/dev/adviqo/calling-service/node_modules/http-link-dataloader/dist/src/BatchedGraphQLClient.js:21:53)
at fulfilled (/Users/pham/dev/adviqo/calling-service/node_modules/http-link-dataloader/dist/src/BatchedGraphQLClient.js:12:58)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:189:7)
(node:5226) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:5226) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Hoang
06/04/2019, 2:02 PMERROR: Whoops. Looks like an internal server error. Search your server logs for request ID: local:cjwhvghbr000b0849nt6jvtno
{
"data": {
"addProject": null
},
"errors": [
{
"message": "Whoops. Looks like an internal server error. Search your server logs for request ID: local:cjwhvghbr000b0849nt6jvtno",
"path": [
"addProject"
],
"locations": [
{
"line": 2,
"column": 9
}
],
"requestId": "local:cjwhvghbr000b0849nt6jvtno"
}
],
"status": 200
}
Stephen Jensen
06/04/2019, 2:14 PM