Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
I want to leverage the new subscriptions support in Apollo Federation but NestJS's docs cause me to think that it isn't supported yet in @nestjs/graphql.
https://www.apollographql.com/blog/announcement/backend/federated-subscriptions-in-graphos-real-time-data-at-scale/#subscriptions-meet-apollo-federation
From https://docs.nestjs.com/graphql/federation:
WARNING
Federation currently does not support subscriptions.
Describe the solution you'd like
Updated docs, support, and example of using subscriptions with Apollo Federation using @nestjs/graphql.
Teachability, documentation, adoption, migration strategy
No response
What is the motivation / use case for changing the behavior?
Build microservices that can be used by a client as one GraphQL API even with subscriptions across those microservices.
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
I want to leverage the new subscriptions support in Apollo Federation but NestJS's docs cause me to think that it isn't supported yet in @nestjs/graphql.
https://www.apollographql.com/blog/announcement/backend/federated-subscriptions-in-graphos-real-time-data-at-scale/#subscriptions-meet-apollo-federation
From https://docs.nestjs.com/graphql/federation:
Describe the solution you'd like
Updated docs, support, and example of using subscriptions with Apollo Federation using @nestjs/graphql.
Teachability, documentation, adoption, migration strategy
No response
What is the motivation / use case for changing the behavior?
Build microservices that can be used by a client as one GraphQL API even with subscriptions across those microservices.