gsala
07/20/2020, 2:05 PMIn fact, there are valid use-cases where you have an entity with its own life-time, like a HTTP connection, and a client code in another module of your application making a request in its own scope. You should be able to easily combine them so that request is restricted to both life-times. Currently, this is cumbersome to implement.What's the right approach to combine two different scopes/lifecycles when launching a coroutine? In my case I have a BLE connection which creates a scope bound to the lifecycle of the connection, and I'd like a client to be able to launch a task to send a message, but also within the scope in which this client lives. This is for an Android project, so client would normally be a Fragment or ViewModel
streetsofboston
07/20/2020, 2:42 PMgsala
07/20/2020, 4:14 PMrepoScope
not affecting the uiScope