:wave: hey i am thinking of implementing pagination using the new incubating cache artifacts. is the...

# apollo-kotlin

[agrosner]

👋 hey i am thinking of implementing pagination using the new incubating cache artifacts. is there any good examples combining cache, pagination, and watch ?

[John O'Reilly]

I think @bod had been looking at this as well?

[mbonnin]

The best place until we stabilize everything would be the integration tests:
https://github.com/apollographql/apollo-kotlin/blob/99590381c4dfbeed2b72665da6df6b[…]s/pagination/src/commonTest/kotlin/CursorBasedPaginationTest.kt

[mbonnin]

The parent folder contains examples for various kinds of pagination (offset, cursor, relay, etc...)

[agrosner]

i saw that. what i am trying to understand is , when I watch a query with pagination parameters (say a limit, offset), when I watch it, will it watch the entire set of data in the cache, or only the first x number of records?

[mbonnin]

It'll watch the entire set of data

[mbonnin]

That's the main goal actually. It does this by ignoring the pagination parameters in the cache key

[mbonnin]

So everything is "accumulated" in the same cache key

[agrosner]

oh awesome . so my next follow up is, when I use something like androidx pagination, how do this change the equation? in the sense that we watch the entire set. but with androidx pagination, im guessing we just invalidate the source when the watch emits?

[mbonnin]

Right, excellent question for which I don't have an excellent answer...

[mbonnin]

You might want to take a look at https://github.com/joreilly/Confetti/pull/57/files#diff-d7af879656ae90af15d29ed856e8bf05c0938bc0f8ce09d9cb2624388d31c950R81

[agrosner]

ah i see. so using query still, but pulling from cache or network at will. interesting!