A modern programming language that makes developers happier.

kotlinlang

:question:  How do the incubating cache artifacts treat paginated query responses differently when specifying `paginationArgs` as part of a field policy at the moment? I assume there are benefits (or will be benefits to come down the line?) :smile:

The main benefit is that it allows to use the same cache keys for multiple pages

It does require some special handling in order to "merge" the different pages as they come in. See <https://github.com/apollographql/apollo-kotlin/blob/99590381c4dfbeed2b72665da6df6b2a9a941ac9/tests/pagination/src/commonTest/kotlin/OffsetBasedWithArrayPaginationTest.kt#L166|https://github.com/apollographql/apollo-kotlin/blob/99590381c4dfbeed2b72665da6df6b[…]ion/src/commonTest/kotlin/OffsetBasedWithArrayPaginationTest.kt>

Bottom line is `paginationArgs` are ignored when computing the cache key for a given object

So if you have say:
```type Query @fieldPolicy(forField: "authors", paginationArgs: "first, after") {
  authors: [Author]
}```
And this query:
```{
  authors(first: 50, after: 0) {
    id
  }
}```
Then the cache key will always be computed as `QUERY_ROOT.authors` (instead of `QUERY_ROOT.authors({"first": 50, "after": 0})` )