Bryn Cooke

Not on the docs team but... My preference is for Approach 1. The other approach still means committing every release. Also, at the moment we have a weird situation where...

I have been hitting this issue and am able to reproduce by running an integration test in a loop. Looks like it is possibly related to this: https://github.com/metrics-rs/quanta/issues/61 The stacktrace...

We should also talk about where the router config fits into all of this.

> i'd love if we could just have it be a command! what command do we use to start this subgraph? Just want to give some perspective from a Java/Rust...

For auto-detection of subgraphs does a full scan take place? Or just well known ranges?

> > The cache is loaded and emptied over a fairly tight iteration in the export function > > Where is it emptied? Is there a case where it could...

If the perf drop for small responses is marginal then would avoid adding extra config for this. Just enable it by default.

I think we should avoid yaml config and rely on Rhai for this one.

This sounds like contracts: https://www.apollographql.com/docs/studio/contracts/ Currently the router only allows one contract variant, but maybe this could be relaxed such that a router could support multiple variants and switch based...

It's a possibility. At this stage I'm not sure how much demand there is for this. Pinging @prasek in case others have asked.