Roman Vasilev

The only right way to add unexisting field in prisma schema to graphql schema is `@ResolveField` But if you are building federated graphql, you can try `@Directive` https://github.com/unlight/prisma-nestjs-graphql#directive https://docs.nestjs.com/graphql/federation#code-first-1 But...

https://github.com/unlight/prisma-nestjs-graphql/issues/116

1. If you hide all filed in class, it's maybe better to make an abstract class from model? See https://docs.nestjs.com/graphql/resolvers#generics https://github.com/unlight/prisma-nestjs-graphql#objecttype 2. You can play with `@HideField` settings https://github.com/unlight/prisma-nestjs-graphql#hidefield And...

I found it in prisma, but indeed countArgs is not generated. Can you provide nestjs resolver code where potential countArgs class will be suitable?

They are compatible in terms of assignment: ```ts { const x: UserGroupByArgs = { by: [UserScalarFieldEnum.id], }; let p: Prisma.UserGroupByArgs = { by: [UserScalarFieldEnum.id], }; p = x; // No...

I was going to create also, If you create, drop here a link

Workaround is obvious: disable type check by `@ts-ignore` or by converting to `any` type, or make explicit type coercion: ``` type UserGroupBy = Parameters[0]; const x: UserGroupByArgs = { by:...

I'm not sure that understand the reason to hide enum. Making model abstract make sense if you want extends and override some fields, but how you will extend enum and...

Are you removed all fields from all models with this enum type?

I added `@HideField({ input: true, model: true, output: true })` to my example https://github.com/unlight/prisma-nestjs-graphql/blob/4f2cb69b349fda560b5a83780778ad2f8d7594c6/prisma/schema.prisma#L59 And enum Role is disappeared from schema, despite `@generated/prisma/role.enum.ts` in requiring during application start and `registerEnumType(Role,...