question How do the incubating cache artifacts treat pagina kotlinlang #apollo-kotlin

Channels

100daysofcode

100daysofkotlin

100daysofkotlin-2021

androidgithubprojects

cincinnati-user-group

competitive-programming

event21-community-content

java-to-kotlin-refactoring

jvm-ir-backend-feedback

kotlin-multiplatform-contest

kotlinultimatechallenge

myndocs-oauth2-server

naming

navigation-architecture-component

practical-functional-programming

proguard

prozis-android-backup

refactoring-to-kotlin

russian-kotlinasfirst

skia-wasm-interop-temp

stayhungrystayfoolish

swagger-gradle-codegen

tricity-kotlin-user-group

Title

Seb Jachec

08/02/2022, 9:52 AM

❓ 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?) 😄

mbonnin

08/02/2022, 9:54 AM

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/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})

)

Seb Jachec

08/02/2022, 10:00 AM

Ah great, makes sense, thanks!

mbonnin

08/02/2022, 10:08 AM

You're welcome!

3 Views

#apollo-kotlin Join Slack