A few weeks ago, one of our customers came to us with an interesting problem: they wanted explicit and granular control over the descriptions that were propagated to their federated graph. As I'm sure you're aware, most constituents of a GraphQL schema may define a description; and an instance of a constituent (coordinates) could appear in multiple subgraphs—each with its own bespoke description. However, only one description can be propagated to the federated graph.
