We are in a scenario where we created a few different prisma services, merged them in 1 unified graphql server (and extended the types for cross boundaries purposes). Now we are creating different graphql servers to use the unified graphql server. It would be amazing to create these in a

nexus-prisma

way!

You can use nexus with whatever you want. It uses the same resolver methods and is just a way of declaring your front-facing schema. One benefit of using nexus-prisma is that you have access to all of your types that Prisma has generated. But you can successfully use it without. I recently did a mini-test with nexus, so if you have some questions - feel free to ask either here or send me a PM.

@Jenkins Sorry I must not have been clear enough. I wish to take an existing graphql server as a starting point to create another graphql server. I don’t want to re-create my types in code first, I would like to be able to expose them/ hide them or extend them. Exactly like you do on

nexus-prisma

. Since

nexus-prisma

takes they

prisma-client

as a starting point. I was thinking I could create graphql-bindings to do the same.

Aaaah, I see. Sorry - rereading your post I should've caught that. I would then probably have a look at the relation between

nexus-prisma

and

nexus-prisma-generate

and see if you can replicate the behavior. That or tag one of the developers, so that they might give their input. I'm just a regular user, and I have idea of the inner workings of nexus. I just know that I like using it 😛

Cheers, I like it too, but I can’t fully enjoy it in my current scenario 🙂

Like a

nexus-interface

of sorts.

yes!

I totally agree there. That would make the extension of nexus much easier for people, and possibly even increase the speed at which other ORMs could apply nexus as a solution.

I will open an “issue” on the repo