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
kind of similar to graphql-nexus/nexus#69 but there where some major changes since then so I don't know if commenting on this issue makes sense.
My question:
Is it possible to use a type from the Prisma namespace as argument type like:
t.field("createCompany",{type: "Company",args: {secret: nonNull(stringArg()),// SOME OTHER ARGSdata: arg({type: Prisma.CompanyCreateInput}),// USE PRISMA TYPE AS ARG},asyncresolve(_root,args,ctx){//... logic}});
the error states that Property 'CompanyCreateInput' does not exist on type 'typeof Prisma' but the type CompanyCreateInput is definitely exported in the index.d.ts of .prisma/client.
The text was updated successfully, but these errors were encountered:
I have similar question, but not quite. I am fine being able to access them through a string, my only issue is that there aren't enough field types available.
For example, only the ModelWhereUniqueInput is generated, but not ModelWhereInput, which would allow me to implement a custom "where" field without the need to create a custom Input and miss out on the advanced filtering.
I think at least all aggregate fields (from ModelAggregateArgs) should be generated.
kind of similar to graphql-nexus/nexus#69 but there where some major changes since then so I don't know if commenting on this issue makes sense.
My question:
Is it possible to use a type from the
Prisma
namespace as argument type like:the error states that
Property 'CompanyCreateInput' does not exist on type 'typeof Prisma'
but the typeCompanyCreateInput
is definitely exported in theindex.d.ts
of.prisma/client
.The text was updated successfully, but these errors were encountered: