Feature Request: Codegen'd resolvers

[prisma-labs]

Feature Request: Codegen'd resolvers

[kbrandwijk]

@LawJolla We have implemented forwardTo in the latest release. Examples are coming, but you can basically replace your resolver function with a simple forwardTo('db') if you want to forward a call 1-on-1 (so same query name and arguments) to an underlying binding. See https://gist.github.com/kbrandwijk/6e693f1cad585cb74fd8e022c7277394#file-query-ts-L11 for a small snippet. Do you think that this sufficiently covers your use case?

[marktani]

Here's an example: https://github.com/graphcool/graphcool/tree/examples-1.0/examples/resolver-forwarding 🙂

[kbrandwijk]

Thank you for this feedback. There are different ways to improve this. Having these bindings generated so you can easily call existing queries and mutations is the first step towards that goal.

One of the options I am personally looking at is a way to 'extend' on what graphql-import offers to also work on resolvers (basically saving you from having to define this resolvers manually completely). However, looking at common use cases, it didn't seem that common to reuse existing queries or mutations exactly 1-on-1.

[LawJolla]

@kbrandwijk I think that hits the use case dead on! Great implementation! Makes a ton of sense. Thanks for your hard and great work!

[kbrandwijk]

Closing, as this use case is apparently sufficiently covered by this feature.