You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Supergraph API queries using the mutation field \"Mutation.f\" at top-level must be satisfiable without needing to call that field from multiple subgraphs, but every subgraph with that field encounters satisfiability errors. Please fix these satisfiability errors for (at least) one of the following subgraphs with the mutation field:
452
+
- When calling \"Mutation.f\" at top-level from subgraph \"A\":
453
+
The following supergraph API query:
454
+
mutation {
455
+
f {
456
+
y
457
+
}
458
+
}
459
+
cannot be satisfied by the subgraphs because:
460
+
- from subgraph \"A\":
461
+
- cannot find field \"F.y\".
462
+
- cannot move to subgraph \"B\", which has field \"F.y\", because type \"F\" has no @key defined in subgraph \"B\".
463
+
- When calling \"Mutation.f\" at top-level from subgraph \"B\":
464
+
The following supergraph API query:
465
+
mutation {
466
+
f {
467
+
x
468
+
}
469
+
}
470
+
cannot be satisfied by the subgraphs because:
471
+
- from subgraph \"B\":
472
+
- cannot find field \"F.x\".
473
+
- cannot move to subgraph \"A\", which has field \"F.x\", because type \"F\" has no @key defined in subgraph \"A\".
474
+
`
475
+
]);
476
+
});
477
+
478
+
it('errors normally for mutation fields that are not actually shared',()=>{
- cannot move to subgraph "B", which has field "F.y", because none of the @key defined on type "F" in subgraph "B" are resolvable (they are all declared with their "resolvable" argument set to false).
520
+
`
521
+
]);
522
+
});
523
+
524
+
it('succeeds when queries do not require multiple calls to mutation field',()=>{
0 commit comments