@Skona27 Hi, thanks 👍 I hope I can answer your question.

Yes currently the code requires duplicates between the prisma schema and the graphql schema.

1. Database schema:schema.prisma describes the model and thus the table created for this model.
2. GraphQL schema:user.model.ts and any other models describes the response value of youruser type for your GraphQL queries

How to resolve the duplicates for now?
It is currentlynecessary to have duplicate code once inschema.prisma and once for your GraphQL schema.

One idea would be to implementUser from prisma client for your graphql model to always keep those prisma and graphql models in sync.

import{User}from'@prisma/client';import{PostModel}from'../post/post.model.ts';@ObjectType('User')exportclassUserModelextendsBaseModelimplementsUser{email:string;  @Field({nullable:true})firstname:string;  @Field({nullable:true})lastname:string;role:Role;  @HideField()password:string;posts:PostModel[];}

Another option might be in the featuretypegraphql-prisma

And in the near feature - when Prisma SDK will be ready - the typegraphql-prisma integration will also allow to use a code-first approach to build a schema.prisma and GraphQL schema at once, using classes with decorators as a single source of truth. Stay tuned! 💪

There is also an typegraphql integration for nestjstypegraphql-nestjs with somecaveats.