Hi, new Primsa-er (Prisma-ite?) here. Enjoying working with it so far, but wanted to get some best practice advice from the community. Many of the models in our app are likely to have a large number of simple fields (just the nature of our domain), so mirroring the model data between the

schema.prisma

and Nexus

schema.ts

files will become tedious for our team pretty quickly. It seems that the Prisma Nexus plugin might help with this, but it looks to be in some sort of in-between state. I looked at TypeGraphQL as well but wasn’t sure if that actually would solve this specific issue. It looks like Pal.js might do solve this, though, so I wondered if that’s what folks are considering a best practice for this at the moment. Also have heard others say that maintaining separation between database and gQL schemas is actually the best practice, though I’ve yet to come up against a use case in our app that makes this clear. Open to all thoughts and ideas. Thanks!

@Evan McDaniel 👋 Yes TypeGraphQL and Pal.js will achieve exactly what you want i.e. mirroring the model b/w

schema.prisma

and your GraphQL schema.

OK, thanks for the info @Ryan. Much appreciated. I will look into them.