Benoit 'BoD' Lubek

Could Fragments help a bit?

Closing for now as the schema based [data builders](https://www.apollographql.com/docs/kotlin/testing/data-builders/) have been available. Don't hesitate to re-open if needed!

Hi! It looks like the backend replies with a `401` error, which in Apollo Kotlin means that it will not treat it as a valid GraphQL response, but a lower-level...

With Apollo v2, you don't need to enable anything specifically - you can get the body by implementing `onHttpError` on your callback, like so: ```java @Override public void onHttpError(@NotNull ApolloHttpException...

Closing this for now, don't hesitate to re-open if needed.

A bit of follow-up: I tend to agree with all of this :). With this "front-end" approach, the only benefit is to avoid rewriting some components (+ having to "backport"...

Closing for now, as we're going with the other approach of rewriting (instead of writing wrappers) for the new runtime

Hi! 👋 There's a drawback to have 2 services for the same schema like this: the files are generated twice. It would probably make more sense to have 2 modules...

> since we're doing a library, a new module means a new artifact to publish and we want to limit those. Oh yes that makes perfectly sense! Especially if one...

[Here's](https://github.com/prasek/supergraph-demo-fed2/pull/1/files?w=1) how I added the delay. And the curl: ``` curl 'http://localhost:4000/' -H 'content-type: application/json' --data-raw $'{"query":"query Product($productId: ID!) {product(id: $productId) {dimensions {size} ... on Product @defer {delivery { estimatedDelivery...