Benoit 'BoD' Lubek

> MockServer does not map the requests to responses, it only adds them to a queue That's correct currently. About improving MockServer, thanks for the insight! Yes we're certainly thinking...

There is now a way to control MockServer responses via [`MockServerHandler`](https://github.com/apollographql/apollo-kotlin/blob/05f2a3295517fb7a64c2259c38b453a37f3c4d19/libraries/apollo-mockserver/src/commonTest/kotlin/com/apollographql/apollo3/mockserver/test/CustomHandlerTest.kt#L33). Closing this issue for now, don't hesitate to re-open if needed!

Hi! 👋 Thank you for reporting this! From what I am gathering online it's not 100% clear whether this can happen when individual rows are too big, or if it...

Clearing it at logout sounds good to me 👍. Even though I suspect most users don't logout often (well that depends on the app of course). The reason I asked...

Hi! If you declare your variables as non nullable (with `!`) they won't be generated as optional. Something like: ```graphql query LoginUserQuery($phone_no: String!, $password: String!) { ```

You can define a default value on query arguments, like this: ```graphql query LoginUserQuery($phone_no: String = null, $password: String!) { ``` this will generate something like: ```kotlin public data class...

Another potential use-case: have the generated models implement `Serializable` or `Parcelable` so they can easily be passed around in Intents, or in a [navigation graph](https://developer.android.com/guide/navigation/navigation-pass-data).

Another potential use case: the ability to make the generated types `internal` or not depending on custom logic (see #4334)

This can also be used to add getters/setters in Java models (#4210)

Also, https://github.com/apollographql/apollo-kotlin/issues/4253