You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there an existing issue that is already proposing this?
I have searched the existing issues
Is your feature request related to a problem? Please describe it
Not exactly a problem, but today graphql subscription is not supported using federation.
There is a explicit throw in the code about it here
// class ApolloFederationDriverif(options.installSubscriptionHandlers||options.subscriptions){// TL;DR <https://github.com/apollographql/apollo-server/issues/2776>thrownewError('No support for subscriptions yet when using Apollo Federation',);}
Describe the solution you'd like
Graphql clients will be able to use subscription calling the federated service/gateway
Not 100% sure how it would be implemented.
IMHO, no migration is needed
What is the motivation / use case for changing the behavior?
We have a microservices infrastructure and would like to have different services exposing subscriptions, so the client (ui / front) would be able to subscribe only knowing the federation gateway endpoint
The text was updated successfully, but these errors were encountered:
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
Not exactly a problem, but today graphql subscription is not supported using federation.
There is a explicit
throw
in the code about it hereDescribe the solution you'd like
Graphql clients will be able to use subscription calling the federated service/gateway
Teachability, documentation, adoption, migration strategy
Not 100% sure how it would be implemented.
IMHO, no migration is needed
What is the motivation / use case for changing the behavior?
We have a microservices infrastructure and would like to have different services exposing subscriptions, so the client (ui / front) would be able to subscribe only knowing the federation gateway endpoint
The text was updated successfully, but these errors were encountered: