Subgraph locations aren't always reported (i.e. in the case of graphql-js errors during composition). This results in a UX where schema authors are given an error without being told where to resolve it.
To reproduce, compose:
type Query @myUndefinedDirective {
hello: String!
}
Note the resulting composition errors (Unknown directive @myUndefinedDirective) don't contain the subgraph info that would be useful in output.
Subgraph locations aren't always reported (i.e. in the case of graphql-js errors during composition). This results in a UX where schema authors are given an error without being told where to resolve it.
To reproduce, compose:
Note the resulting composition errors (
Unknown directive @myUndefinedDirective
) don't contain the subgraph info that would be useful in output.