Add routing support for generic node resolver

[saerdnaer]

Component(s)

No response

Is your feature request related to a problem? Please describe.

Some schema design specifications e.g. Relay require a generic resolver node(id: ID!): Node which, in a federated subgraph forwards the request to the corresponding routing-url / subgraph server e.g. via a domain/entity prefix in ID.

For example, a ID like foo:cms:123 must be forwarded to the CMS subgraph as node(id: ID): Node, while foo:coral:comment:123 should go to the comments subgraph, foo:epg:broadcast:123 to the EPG domain, and so on.

type Query {
  node(id: ID!): Node
  …
}

interface Node {
  __typename: String!
  id: ID!
}

type Page implements Node {
  id: ID!
  title: String!
  …
}

type Article implements Node {
  id: ID!
  title: String!
  …
}

type Comment implements Node {
  id: ID!
  title: String!
  …
}

Describe the solution you'd like

Some method/hook inside of cosmo-router to define the logic how queries to the node(id: ID!) should be resolved

Describe alternatives you've considered

One could deploy an additional subgraph in on own service which could proxy the requests to the corresponding subgraph.

Additional context

Additional resources

• https://graphql.org/learn/global-object-identification/#node-interface
• https://graphql.org/learn/global-object-identification/#node-root-field
• https://relay.dev/graphql/objectidentification.htm

[github-actions]

WunderGraph commits fully to Open Source and we want to make sure that we can help you as fast as possible.
The roadmap is driven by our customers and we have to prioritize issues that are important to them.
You can influence the priority by becoming a customer. Please contact us here.