You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/migration/4.0.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -227,9 +227,9 @@ For more control over the exception, use `toFlow()` and collect the different `A
227
227
228
228
In Apollo Kotlin 3, when using the normalized cache, you could set `emitCacheMisses(Boolean)` to `true` to emit cache misses instead of throwing.
229
229
230
-
In Apollo Kotlin 4, this is now the default behavior and`emitCacheMisses(Boolean)` has been removed.
230
+
In Apollo Kotlin 4, cache misses always emit a response with `response.exception` containing a `CacheMissException`.`emitCacheMisses(Boolean)` has been removed.
231
231
232
-
With the `CacheFirst`, `NetworkFirst` and `CacheAndNetwork` policies, cache misses and network errors are now exposed in `ApolloResponse.exception`.
232
+
With the `CacheFirst`, `NetworkFirst` and `CacheAndNetwork` policies, cache misses and network errors are now exposed in `ApolloResponse.exception`.
0 commit comments