support for multiple services? about prisma-binding HOT 6 CLOSED

What you could currently do if you manage your Prisma backends outside of your Graphl Server project, is use prisma-bindings and add the Prisma backends as regular endpoints (so without the prisma extension in the config). That way, they would behave like any other endpoint.
It would allow you to add two Prisma bindings to your context. Is your example, you are adding two endpoints to a single binding, but I don't see any benefit over using two bindings.

from prisma-binding.

I have a use case that involves multiple Prisma APIs to bind against. After trying to create two separate Prisma objects in context, I noticed that they both ended up pointing to the same schema and endpoint. If I understand the conversation correctly so far, that means @kbrandwijk 's suggestion will not behave as expected.

The problem appears to be rooted in the global variable for remoteSchema https://github.com/graphcool/prisma-binding/blob/2117ddffdad990867616505ef80f618e4628a21d/src/Prisma.ts#L16. If I construct a Prisma pointed at a particular schema, then a second one, both instances will use the first schema provided due to the check on line 59 https://github.com/graphcool/prisma-binding/blob/2117ddffdad990867616505ef80f618e4628a21d/src/Prisma.ts#L59.

I haven't used TypeScript before, but I could try to put in a patch. Changes were introduced in 67612e9; any fix would probably benefit from understanding why the remote schema caching was changed.

from prisma-binding.

@a-type That is a very good point, thank you for bringing this up. I have created #81 for this.

from prisma-binding.

@a-type would you be open creating a PR for this (see #81)?

from prisma-binding.

@schickling Sure, I'll look into doing that soon. Be advised that I've never written Typescript before, but hopefully this is a fairly trivial change.

from prisma-binding.

Fixed with #81

from prisma-binding.