Support selective forwarding about graphql-middleware-forward-binding HOT 4 CLOSED

hey @carstenbaumhoegger!

thank you for such nice feedback! I have unfortunately not. I was thinking about it but couldn't find a meaningful API solution.

This package is based on forwardTo property which is exposed by graphql-binding as well as prisma-binding. It's extremely easy to use this one as well. You can read more about it here https://github.com/prismagraphql/prisma-binding/blob/master/README.md#forwardto .

I would love to improve this package; therefore, if you have any idea of how we could make your case work with a general API I would be more than happy to hear it!

I hope this helps you solve your case. 🙂

from graphql-middleware-forward-binding.

@carstenbaumhoegger just added support for this, check out 30bfb4a! 🎉

from graphql-middleware-forward-binding.

hey @maticzav !
Sorry for my late response.

The changes you made are great! 🎉

I would have another usage for this selective forwarding but with some kind of "blacklisting". So instead of providing all queries and mutations that should be forwarded, I'd like to provide all, that should NOT be forwarded and handled by graphql-yoga 😄

Do you know a solution for this problem?

Thanks in advance
Carsten

from graphql-middleware-forward-binding.

Hey man, sure thing! I am glad you like it 🍻 I think the easiest way to achieve blacklisting like feature is by copying Query and Mutation types and just removing the fields you don’t need.

I also think that we don't need explicit functionality for blacklisting because of this since it wouldn't make sense, at least that's what I think 😄

You probably know how the rest of the implementation should work 🎉

from graphql-middleware-forward-binding.