Unify response from delegate and request about prisma-binding HOT 4 CLOSED

@schickling Can I get your feedback on this issue, because it affects the way resolvers are implemented.

from prisma-binding.

Sorry for the delay @kbrandwijk. So far that was actually intended. request is meant as a "ready-to-use" version of graphql-request (therefore the name). Can you elaborate more on some concrete problems you see with the current design?

from prisma-binding.

Because it is used in a context of resolvers, where all resolvers (built-in or delegated) return the data itself. That means that if I run into a use case where a binding delegate call is not sufficient, and I just want to specify my own query and call request on the binding, I suddenly get the data in a different format. I personally think it would be best (within the context of bindings) that they are interchangeable.

from prisma-binding.

Hey 👋, I believe this issue is no longer in sync with the current version of prisma-binding. In need for gaining a better overview of the issues facing the current version, I'll close it.

Feel free to reopen the issue if you believe we should further discuss its context. 🙂

from prisma-binding.