I see at this https://www.prisma.io/docs/1.26/get-started/03-build-graphql-servers-with-prisma-TYPESCRIPT-t201/ has

The Post and User types are straightforward re-definitions of the models specified in datamodel.prisma, except that the Prisma-specific directives have been removed.

How can i avoid re-definition of the models on the schema?

This will be solved by Nexus and the

nexus-prisma

plugin. https://www.prisma.io/blog/introducing-graphql-nexus-code-first-graphql-server-development-ll6s1yy5cxl5/

Indeed 🙂 👀

Oh @marcus @nikolasburk so good

Good news guys @marcus @nikolasburk! With this feature it will not be necessary to code the resolvers? I need to add a custom query but I don't want to declare and code the resolvers, I want to use them from cli, I only want to extend, for example, one query and do some server code, like executeRaw but executing a npm script internally (introspect and re-deploy).

No you won't have to code resolvers when using exposing/extenting prisma types 👍

Ok, when it will be available the

nexus-prisma

plugin approximately?

Very, very soon 👀