Hi @sefi18, below are my findings…
The main issue is in the SDL returned. As you mentioned above the
schema {
query: Query
}
Is causing problems. I am not sure if this is a bug in our library or the Java one. This can easily be by passed. We can route the SDL requests through an API that transforms the result and remove that bit.
The other problem I noticed is that one of the graphs’ SDLs has a query with an empty body which is again causing a problem.
The extend vs @extends seem to work fine regardless.
My question is, how will this work with multiple subgraphs adding entry points to the Query type? Because the SDL does not add extend or @extends to the Query type.