Skip to content
This repository has been archived by the owner on Sep 2, 2022. It is now read-only.

Allow prisma-client to take null as input values #3622

Closed
Weakky opened this issue Nov 29, 2018 · 1 comment
Closed

Allow prisma-client to take null as input values #3622

Weakky opened this issue Nov 29, 2018 · 1 comment

Comments

@Weakky
Copy link
Contributor

Weakky commented Nov 29, 2018

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-client does 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.

@nikolasburk
Copy link
Member

Closing as a duplicate of prisma/prisma#3621

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants