lucid_frog
03/09/2018, 9:26 PMDateTime
in the seed.graphql ?
as a string
or… ?matty
03/10/2018, 3:13 AMmatty
03/10/2018, 3:13 AMmatty
03/10/2018, 3:20 AMRoman
03/10/2018, 3:21 AMsajmil
03/10/2018, 3:23 AMallpwrfulroot
03/10/2018, 3:28 AMMcArthur
03/10/2018, 3:51 AMLiam
03/10/2018, 4:06 AMlucid_frog
03/10/2018, 1:24 PMset: Override the existing list with an entirely new list.
https://www.prismagraphql.com/docs/reference/prisma-api/mutations-ol0yuoz6go#updating-nodes
But in practise, let’s say I have numbers: [1, 2, 3, 4]
and then proceed to do a numbers: { set: [9] }
(in a mutation.update) I would expect numbers
to return [9]
, but instead, I get numbers: [9, 2, 3, 4]
Any idea as to why that is ?lucid_frog
03/10/2018, 1:24 PM[Scalar list mutations]
terion
03/10/2018, 3:33 PMTroyZ
03/10/2018, 3:57 PMkuldar
03/10/2018, 4:01 PMgraphq-yoga
?) resolver that loops over an array and sends create
mutations one by one?terion
03/10/2018, 4:16 PMsteve
03/10/2018, 5:41 PMsteve
03/10/2018, 5:44 PMVdrizzle
03/10/2018, 8:39 PMjamiehalvorson
03/11/2018, 7:38 AMsuchy
03/11/2018, 10:01 AMsignor_busi
03/11/2018, 10:36 AMsignor_busi
03/11/2018, 10:38 AMsignor_busi
03/11/2018, 10:38 AMjjaybrown98
03/11/2018, 11:56 AMMaxime Scibetta
03/11/2018, 2:52 PMShaikat
03/11/2018, 3:36 PMDaniel K.
03/11/2018, 3:58 PM<http://docker:4466/prisma/dev>
I get the playground, but there is no schema
I would be expecting to be able to interact with database schema through it
Could that be a bug coming from the fact, that my Docker is running on a separate IP address, not localhost?ehodges
03/11/2018, 4:04 PMsteve
03/11/2018, 5:36 PMqsys
03/11/2018, 6:38 PM- operation: Users.read
authenticated: true
query: hasRoleAdmin.graphql
When having a function of type operationBefore
, how can I add authentication/authorization before that function? So:
makeUser:
type: operationBefore
operation: User.create
handler:
code:
src: ./src/befores/createUser.ts
environment:
...
Inside the src/befores/createUser.ts
function, I call an external service, and if that one succeeds, another user can be created. However, this logic may only be executed when the user has proper rights. For now, it seems that adding:
- operation: Users.read
authenticated: true
query: hasCreateUserPermission.graphql
the query logic is executed 'after' the operationBefore query, which leads to weird results (on the external service, some stuff is added, but not on graphcool, since the user is not authorized to do so. I'd prefer to have the authentication logic be executed before the request pipeline.
What is the intended behaviour?
And if it is intended that the authentication is executed as the last one in the request pipeline, how to move it to the front of the pipeline?