kotlin-coroutines-structured-concurrency

To refactor a stored CoroutineScope, remove the property and expose suspend functions instead, delegating lifecycle ownership to the caller. This ensures work is expressed through suspending APIs rather than non-suspending launches.

Moving coroutine launches out of init blocks ensures cancellation and error semantics are explicit. It enforces lifecycle ownership by the caller, requiring mapping to lifecycle-scoped contexts like viewModelScope.

Structured concurrency in Kotlin coroutines means lifecycle ownership stays with the caller and work is expressed through suspending APIs. It prevents misuse like storing CoroutineScope or using fire-and-forget calls.

You validate changes by testing with runTest. This confirms that removing stored CoroutineScope and converting to suspending APIs maintains correct cancellation and error semantics across repositories and UI layers.

Yes, this refactor applies to codebases with UI state holders and repositories. It provides guidance for coroutine boundaries, outlining patterns for explicit launch sites and lifecycle-bound scopes across data sources and UI layers.

Fix fire-and-forget calls by removing stored CoroutineScope and converting to suspending APIs. This enforces lifecycle ownership by the caller and requires mapping to lifecycle-scoped contexts like viewModelScope.