Public facing vs Admin facing apis
cipriancaba opened this issue · comments
Been trying to figure out an elegant solution for creating 2 different graphql endpoints. One would be the one with CRUD operations, which will be admin facing and the other would be public(client) facing and will just contain a subset of the operations and potentially some custom resolvers.
The complication comes from the fact that I need to use one prisma schema and the generated graphql schemas would obviously be different. Also would need to disable the crud resolvers altogether in one of the instances.
Any idea on how I could achieve this?
Been using a gateway before that would proxy the graphql requests and only expose a subset of the schema, but would like to avoid this if possible.