What's the benefit of having bindings on the context about prisma-binding HOT 2 OPEN

You should consider this as a best practice (and requirement) for using the dataloader pattern which is used by most bindings (or more precisely: injected through the links).

I'm happy to explore other ways to lift this requirement!

from prisma-binding.

Let's explore the possibilities for taking them out of the context. I think it will make the code a lot clearer (less nesting). For cases where something needs to happen for every request, I also don't think the context is the best place. A middleware function seems more suitable. The context is quite a 'heavy' object to pass around to all the resolvers in a large schema, and having these huge binding objects on them doesn't help. But I haven't done any measurements to support this (yet).

from prisma-binding.