Duplicated _entities in federation
ramiel opened this issue · comments
As in issue #643 should it be similar for _entities?
I'm sorry but I don't understand what you are talking about. Can you clarify and make an example?
Sorry for the poor description. I want to ask another question actually, that includes an answer to this issue as well. In the documentation is written:
A GraphQL server can act as a Gateway that composes the schemas of the underlying services into one federated schema and executes queries across the services. Every underlying service must be a GraphQL server that [supports the federation](https://www.apollographql.com/docs/federation/supported-subgraphs/).
From the link it looks like mercurius does not support some critical feature. Is it possible to use mercurius as underlying service, in a federation?
According to announcement of Federation v2, it is patent pending.
While it would be ok for users to make a judgment call for themselves, I do not feel I should include them in the main package. As soon as we have Federation support separated in mercurius-js/mercurius-gateway#1, anybody could fork that project to add those in.
Ok, good to know. Since mercurius can act as gateway I thought it could be used as service as well. My fault. To be honest I can make the service work with mercurius as well, but it's a bit of an hack. I'll leave things unchanged or move to something else like graphql-yoga.
Thank you