You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 2, 2022. It is now read-only.
Is your feature request related to a problem? Please describe.
This is related to graphqlgen, and specifically to prisma-labs/graphqlgen#278 (Everything is already clearly explained here)
GraphQL accepts nullable input fields either as undefined or null. As a result, graphqlgen needs to type all input fields as field: type | undefined | null, or field?: type | null
However, prisma-clientdoes not accept null as input values of queries/mutations, probably because it doesn't make sense in the context of the client.
Unfortunately, this prevents users from passing typed arguments with graphqlgen to prisma-client, because undefined | null !== undefined.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
This is related to graphqlgen, and specifically to prisma-labs/graphqlgen#278 (Everything is already clearly explained here)
GraphQL accepts nullable input fields either as
undefined
ornull
. As a result, graphqlgen needs to type all input fields asfield: type | undefined | null
, orfield?: type | null
However,
prisma-client
does not acceptnull
as input values of queries/mutations, probably because it doesn't make sense in the context of the client.Unfortunately, this prevents users from passing typed arguments with graphqlgen to
prisma-client
, becauseundefined | null
!==undefined
.The text was updated successfully, but these errors were encountered: