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: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -168,7 +168,7 @@ The factorial calculation here is not performed by a single coroutine, but by an
168
168
### 13. Exception Handling
169
169
170
170
This use case demonstrates different ways of handling exceptions using `try/catch` and `CoroutineExceptionHandler`. It also demonstrates when you should to use `supervisorScope{}`: In situations when you don't want a failing coroutine to cancel
171
-
its sibling coroutines. In the use case the results of the successful responses are shown even tough one response wasn't successful.
171
+
its sibling coroutines. In one implementation of this use case, the results of the successful responses are shown even tough one response wasn't successful.
Copy file name to clipboardExpand all lines: app/src/main/java/com/lukaslechner/coroutineusecasesonandroid/usecases/coroutines/usecase13/ExceptionHandlingActivity.kt
-5Lines changed: 0 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -42,9 +42,6 @@ class ExceptionHandlingActivity : BaseActivity() {
Copy file name to clipboardExpand all lines: app/src/main/java/com/lukaslechner/coroutineusecasesonandroid/usecases/coroutines/usecase13/ExceptionHandlingViewModel.kt
0 commit comments