A modern programming language that makes developers happier.

kotlinlang

Disappointed to see the deprecation of CacheAndNetwork, but I kind of understand: <https://github.com/apollographql/apollo-kotlin-normalized-cache/pull/205>
I do understand chaining 2 states has limitations (what if you want CacheAndLocalDatabaseAndNetwork), etc too.  this shorthand is helpful for our react native familiar engineers coming from apollo react client.

Would be nice if it was possible to contribute our own fetch policies with their own set of execution options (or similar?)

`fetchPolicy(FetchPolicy.CacheOnly).toFlow().onCompletion { emitAll(fetchPolicy(FetchPolicy.NetworkOnly).toFlow()) }`

thats pretty verbose...

Thanks a lot for the feedback! One reason for the deprecation is that this policy doesn't play nice with `.execute()` unlike the other ones.


> thats pretty verbose...
True, but you can make it an extension to not repeat it everywhere.


> Would be nice if it was possible to contribute our own fetch policies with their own set of execution options (or similar?)
You can actually! By <https://apollographql.github.io/apollo-kotlin-normalized-cache/kdoc/normalized-cache/com.apollographql.cache.normalized/fetch-policy-interceptor.html|setting> your own `fetchPolicyInterceptor`.  An example <https://github.com/apollographql/apollo-kotlin-normalized-cache/blob/be7d858ca00a3960d5a2e5801d24bb3b8ec30476/tests/store-errors/src/commonTest/kotlin/test/StoreErrorsTest.kt#L779|here>.