Roman Vasilev
Roman Vasilev
Like I suspected, order of fields in class doesnt matter. Some types may not be compatible, in your case with schema above generated UserGroupByArgs is compatible with prisma user.groupBy argument....
Tested on graphql query ```graphql query { groupByUser( orderBy: [{ name: asc }] by: [id, name] ) { id name } } ``` ``` userGroupByArgs = { orderBy: [ {...
Looks like you are facing this issue https://github.com/prisma/prisma/issues/17297
I see different error: Type of property 'AND' circularly references itself in mapped type '{ [K in keyof { AND?: BlogPostScalarWhereWithAggregatesInput | BlogPostScalarWhereWithAggregatesInput[]; ... 9 more ...; authorId?: number |...
Could you provide minimal schema which helps reproduce the issue?
Related https://github.com/unlight/prisma-nestjs-graphql/issues/65
GraphQL does not natively support a BigInt type, as its standard Int type is limited to 32-bit integers. See example in documentation https://github.com/unlight/prisma-nestjs-graphql?tab=readme-ov-file#graphqlscalars
I did not check it yet
Since Prisma 6 types may not be compatible. Please, provde part of the schema to reproduce the issue actual generated class and expected result.
You want different name in graphql schema? You can expose custom name by using ResolveField https://docs.nestjs.com/graphql/resolvers If you want different names in tables, see `@@map` Prisma schema API https://www.prisma.io/docs/reference/api-reference/prisma-schema-reference#map-1