"createSubscriptionResolver" should be allowed to be overridden with a custom resolver as happens with "createResolver" function

[alexandra-c]

I'm working on a project with a multi-tenant micro-services architecture. I have a Main_GraphQL server which imports schemas from other GraphQL services using introspectSchema and makeRemoteExecutableSchema.
Let's assume that tenant1 wants to import schema from GraphQL_Service_1 and tenant2 from GraphQL_Service_2. The tricky thing is that both services have actually the same schema but the resolvers are different.
So what i need is when i get the call from tenant1 to run the resolvers from GraphQL_Service_1 and when i get a call from tenant2 to run the resolvers from GraphQL_Service_2.
I managed to achieve this for Query and Mutations by passing a customCreateResolver to makeRemoteExecutableSchema.
The problem is that makeRemoteExecutableSchema doesn’t use the customCreateResolver function when creating the resolvers for subscriptions but it uses the default one.

Is it possible to allow overriding the subscription resolvers with a custom one as it happens now with the ones for Query and Mutation?

Thank you! I really need this.

[yaacovCR]

In v5 makeRemoteExecutableSchema is deprecated in favor of wrapSchema which acts like transformSchema++, you can specify remote schema options and transforms. Missing piece is to pass a function to provide your own delegating resolver, just requires an additional argument. That would work for queries, mutations, subscriptions.

Folding into #1306

[alexandra-c]

I'll be waiting for the custom delegating resolver parameter to come up then. Thank you. :)

[yaacovCR]

Moving to v5.1, reopening to move any relevant discussion here.

[yaacovCR]

Moved back into v5.0, track #1308

Thank you for pushing on this.

[alexandra-c]

Moved back into v5.0, track #1308

Thank you for pushing on this.

That's realy great! Thank you!!