Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

generating wrong operation input in prisma.graphql #1016

Open
codingfunwoody opened this issue Jan 6, 2021 · 0 comments
Open

generating wrong operation input in prisma.graphql #1016

codingfunwoody opened this issue Jan 6, 2021 · 0 comments

Comments

@codingfunwoody
Copy link

codingfunwoody commented Jan 6, 2021

Problem:
I generated a prisma.graphql and the operation input is different with the old version, suppose the operation input of old version is correct.

old version operation input of prisma.graphql:

input BillingRequestUpdatedisbursementDescriptionsInput {
  set: [String!]!
}

new version operation input of prisma.graphql:

input BillingRequestUpdatedisbursementDescriptionsInput {
  set: [String!]
}

old version dependency:

"@prisma/client": "2.11.0"
"@nexus/schema": "0.18.0",
"nexus-plugin-prisma": "0.24.0",

new version dependency:

"@prisma/client": "2.13.1"
"nexus": "1.0.0",
"nexus-plugin-prisma": "0.27.0",

why i concern this:
i use the prisma.graphql to generate the typescript's type and it's different with the prisma-client type because the prisma.graphql operation input is set as optional

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

No branches or pull requests

1 participant