Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Schema organization in the context of using Schema Stitching directives #360

Open
Drilmo opened this issue Apr 11, 2024 · 0 comments
Open

Comments

@Drilmo
Copy link

Drilmo commented Apr 11, 2024

hello, I use the "schema stitching" part with a gateway and to simplify maintenance and upgrades, I use "stitching directives" in the sub-services to make the links between them.
However, I was wondering if it would be possible to better organize the graph as a whole (all the queries are scattered throughout the documentation, which makes reading a bit complex).

Isn't it possible to use schemas like:

type typeA {
    id: ID!
    name: String!
  }
type Query {
 subServiceA: subServiceAQuery
}
type subServiceAQuery {
 "hello world"
 get(id: ID!): typeA @merge(keyField: "id")
}

I'm asking because I can't figure out how to do it, knowing that @merge can only be used as a root query field. How can I do this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant