impowski
09/09/2018, 11:45 AMzonofthor
09/09/2018, 1:47 PMDaniel
09/09/2018, 8:17 PMDaniel
09/09/2018, 8:17 PMDaniel
09/09/2018, 8:21 PMimpowski
09/09/2018, 8:39 PMupdateUser
they work the same the only difference is that it updates many nodes and return a BatchPayload
. My main concern is to be able to access fields from the same schema inside of update.giacomoguiulfo
09/09/2018, 9:18 PMavdeveloper
09/10/2018, 5:20 AMgraphcool playground --target=dev
It says "function execution error: request to <http://MY_API_SERVER:3100/PATH> failed, reason: connect ECONNREFUSED 127.0.0.1:3100"
Nils
09/10/2018, 7:07 AMNils
09/10/2018, 7:08 AMWhoops. Looks like an internal server error. Please contact us from the Console (<https://console.graph.cool>) or via email (support@graph.cool) and include your Request ID: eu-west-1:simple:cjlv40y0f0v1f0182phsfu1w3
and now I'm also getting that in the dev console in my browser when trying to use the now broken app.Nils
09/10/2018, 7:09 AMDownloading nodes... 625ms
Downloading lists... 279ms
Downloading relations... ✔
WARNING: Error: The download of relations failed. You may get fragmented data. Request ID: eu-west-1:simple:cjlv62k4z18pf0143mczgonc8
at /usr/local/lib/node_modules/graphcool/node_modules/graphcool-cli-engine/src/Output/index.ts:209:41
at SimpleAction.ActionBase.pause (/usr/local/lib/node_modules/graphcool/node_modules/graphcool-cli-engine/src/Output/actions/ActionBase.ts:65:17)
at Output.warn (/usr/local/lib/node_modules/graphcool/node_modules/graphcool-cli-engine/src/Output/index.ts:206:17)
at Exporter.<anonymous> (/usr/local/lib/node_modules/graphcool/node_modules/graphcool-cli-core/src/commands/export/Exporter.ts:100:18)
at step (/usr/local/lib/node_modules/graphcool/node_modules/graphcool-cli-core/dist/commands/export/Exporter.js:32:23)
at Object.next (/usr/local/lib/node_modules/graphcool/node_modules/graphcool-cli-core/dist/commands/export/Exporter.js:13:53)
at fulfilled (/usr/local/lib/node_modules/graphcool/node_modules/graphcool-cli-core/dist/commands/export/Exporter.js:4:58)
at process._tickCallback (internal/process/next_tick.js:68:7)
Nils
09/10/2018, 7:10 AMNils
09/10/2018, 8:04 AManton-b
09/10/2018, 12:01 PMMlyck
09/10/2018, 1:59 PMweakky
09/10/2018, 3:17 PMJerry Jäppinen
09/10/2018, 5:15 PMJerry Jäppinen
09/10/2018, 5:17 PMjdoyle112
09/10/2018, 5:46 PMtomhut
09/10/2018, 7:01 PMBruno Prela
09/10/2018, 7:19 PMBruno Prela
09/10/2018, 7:21 PMBruno Prela
09/10/2018, 7:22 PMBruno Prela
09/10/2018, 7:23 PMkratam
09/10/2018, 7:42 PMonConnect: (connectionParams: any, webSocket) => {
return {
foo: 'bar',
}
But the context
is undefined in the subscription resolver.Stefano T
09/10/2018, 8:31 PMpeter
09/10/2018, 9:11 PMTanner
09/11/2018, 3:43 AMprisma_db_introspection_1.PrismaDBClient is not a constructor
while running prisma instrospect
on step 6 on existing postgres db during the basic tutorial found here https://www.prisma.io/docs/1.16/get-started/01-setting-up-prisma-existing-database-a003/Mark
09/11/2018, 4:14 AMgraphcool export
from graphcool CLI recently?Mark
09/11/2018, 4:15 AMCannot read property 'id' of undefined