Creates CoroutineScope for Decompose component

DecomposeUtils.kt

fun ComponentContext.componentCoroutineScope(): CoroutineScope {
   val scope = CoroutineScope(SupervisorJob() + Dispatchers.Main.immediate)

   if (lifecycle.state != Lifecycle.State.DESTROYED) {
       lifecycle.doOnDestroy {
           scope.cancel()
       }
   } else {
       scope.cancel()
   }

   return scope
}

Usually InstanceKeeper instances outlive the hosting component. So scoping a job that captures the component would be a memory leak. Even though it's discouraged, you can still make all your components retained, so that you the original extension function would work just fine.

Btw, since Essenty version 1.3.0-beta01, Lifecycle#doOnDestroy {} callback is automatically called if the lifecycle is already destroyed. So there is no need to check for DESTROYED state manually.