wabrit

Hi @mefellows do you mean the generated json file?

Apologies for the delay, but I wanted to strip our "real" examples down to the bare essentials necessary to demonstrate the issue: Here's a simple contract (minus the actual test):...

I've hit this same problem; this (decoupling subgraphs via interfaces) is quite a common pattern in monolithic graphs, The only workaround I can see is - to redeclare the interface...

Thanks @pcmanus for that very helpful reply; I understand the issues involved with resolving "dual purpose" enums. My particular case is probably quite edge, as it involves subgraphs which dynamically...

Its certainly worth considering `@inaccessible` as another possible approach, although I suspect it would make orchestration of subgraph restarts/republishing quite complex (and it may be that the subgraph would have...

I think the issue is that the `buildSubgraphSchema` method provided by the `@apollo/subgraph` library doesn't allow for the caller to pass in some directive functions that can be visited _after_...

Note that the above only works for older versions of apollo-server; for 3.5.x the `SchemaDirectiveVisitor` class no longer exists, and the[ new directives pattern](https://www.graphql-tools.com/docs/schema-directives) causes issues when applied to a...

Hi @pcmanus thanks for getting back to me - some answers (and thanks for the suggested hack - I will try that out). I started off with the `SchemaDirectiveVisitor` but...

Unfortunately your suggested workaround didn't work; despite passing `assumeValid: true` as options to `buildASTSchema` so that it doesn't have to worry about federation directives, it stumbles over any `extend type...

Yep a little foreknowledge is good :-) I'm working with federation 2 (at least on the gateway) so as to pick up the latest and greatest. Agree that a callback...