Benoit 'BoD' Lubek

Hi! This could be convenient but could also be a bit dangerous as this will potentially make a lot of network requests in a loop if there are many pages....

Hi! Sorry for the long delay! I think for now a separate artifact would be overkill but we could add this to the main artifact (apollo-runtime) as an `@ApolloExperimental` method....

I'm sorry, I don't understand this sentence "I think I reversed the order for that reason that passing one nameless parameter attached to the onSuccess()."

You are right, it works indeed, so the last part of what I wrote is incorrect. I can't figure out right now what I did that made me think the...

Hi! To be honest it's a weird project (I'm working on the Apollo Android library)which has tons of schemas, including json ones, all over the place for test cases. Not...

@ynkm169 the idea here was to control the expiry per type rather than per query or fragment. Since several queries and fragments can contribute the same fields to the cache...

> Apollo Kotlin does not support partial cache hit. However, I imagine if done per type, you will never have partial cache hit issues since you are always querying part...

I _think_ 2. should be possible but it could be hazardous in the sense that if your field correspond to a record that is also returned by another query (cache...

Our current focus is on version 4 which currently doesn't include this, and is expected to land around ~ Autumn 2023 (see [the roadmap](https://github.com/apollographql/apollo-kotlin/blob/main/ROADMAP.md)), and then we'll probably work again...

@hanssonduck This is currently not being worked on by the team and not planned to be part of v4, but we would certainly welcome a contribution for it. Note: as...