feat(services/gql-subscription): allow custom execute() and subscribe() for other plugin systems

[charlypoly]

Follow-up on #2145:

Update the GqlSubscriptionServiceOptions configuration to allow passing custom execute() and subscribe() function.
This change is required to support GraphQL Server plugin systems such as Envelop and to allow support GraphQL Yoga.

[charlypoly]

Hi @kamilmysliwiec,

Do you know who I could ping to review this short PR?
This is "blocking" us from releasing the GraphQL Yoga driver.

Thank you!

[kamilmysliwiec]

LGTM

[sschneider-ihre-pvs]

@charlypoly does this only work for subscriptions or is there a way to access the executor to attach envelop to the server?

[charlypoly]

@sschneider-ihre-pvs I guess the only way to achieve such a thing would be to create a Nestjs GraphQL driver.

However, please note that we will soon release the GraphQL Yoga Nestjs GraphQL driver which is built on top of Envelop, allowing you to pass plugins in the driver config.

[sschneider-ihre-pvs]

But I don't have yoga, I use the apollofederationdriver

[charlypoly]

@sschneider-ihre-pvs

But I don't have yoga, I use the apollofederationdriver

Looking at the Apollo driver code, I guess it could be possible to pass the executor option as showcased here: https://github.com/dotansimha/envelop/blob/main/examples/apollo-server/index.ts

[sschneider-ihre-pvs]

ok, but how do I get the schema from within the driver?

[charlypoly]

ok, but how do I get the schema from within the driver?

I am not part of the NestJS team, just an outside contributor 🙂

Have you checked the full documentation https://docs.nestjs.com/graphql/quick-start?
This subjects seems a bit out of scope with this PR, maybe a more efficient way would be to open a dedicated issue for it where the NestJS core team could answer