Sylvain Lebresne

@getglad I think the confusion comes from how `@shareable` should be used. And to be fair, it is easy to get wrong and I had a patch to help catch...

@jukben I'm not completely sure this is the same issue. Afaict, you don't seem to be using `@shareable` in particular. But I understand that you have something that worked in...

@jukben gotcha, thanks for the details, that make more sense now :) First, I'll quickly call out that federation has not particular understanding of the Relay Object ID specification. Instead,...

Sorry for the very long silence on this. Fixing this is officially on [the roadmap](https://github.com/apollographql/federation/blob/main/ROADMAP.md#under-consideration) (it's the "Entity interfaces can be spread ..." bullet point) and fwiw I'm personally very...

> @pcmanus Has there been any progress here? Sorry again for the spotty updates. But we have starting working more concretely on the proposal I've laid out in my previous...

Hi @mmanciop. Really sorry about the lack of progress/news here. Ben had his attention go to other places since his last comments, and we've let this fall to the wayside....

It might help to explain this to know the schema and details regarding the subgraphs (are they functioning properly and what are their resolvers in particular). Because I'm not entirely...

Right. So to provide context to other readers, the issue is that federation 1 has a bug when it goes to handling queries like: ```graphql me { id @skip(if: true)...

Thanks for the contribution. I'll admit that I'm personally just a little bit unsure about adding `application/graphql+json` explicitely because: 1. the whole [graphql-over-http](https://github.com/graphql/graphql-over-http) effort is still Stage 0, and the...

Sorry for the delay on this. The issue was due to the fact that the type used within the `@provides` condition was not "reachable" in the subgraph except through external...