This is both Android and coroutines specific but t...

# coroutines

[Rechee Jozil]

This is both Android and coroutines specific but think it may apply to more than just Android:

I'm trying to come up with a way to have our own "global" scope that can also be replaced with a test coroutine scope for unit tests. Anyone have a recommendation or have sort of implementation like this now?

My initial thought is to make the scope injectable via DI (dagger in my case). But not sure if that's overkill vs having some kind of static global scope. Thoughts?

[zak.taccardi]

having some kind of static global scope

Never do this. You make testing harder. Inject your scopes everywhere. Solves all kinds of issues

[zak.taccardi]

When our sdk/app is constructed, we create a global CoroutineScope(dispatchers.default). And we also inject our dispatchers too.

We disallow any reference to Dispatchers.XXX outside of this file, as well as GlobalScope

Untitled.kt

[Sinan Kozak]

Create a scope in app class, expose it with interface and inject that interface or provide scope from that application in constructor.

[Rechee Jozil]

@zak.taccardi how do you prevent outside scope usage? Is it just honor rule or maybe lint?

[Sinan Kozak]

https://github.com/LukasLechnerDev/Kotlin-Coroutine-Use-Cases-on-Android. Usecase 14 iirc

[zak.taccardi]

what do you mean by outside scope usage? Like someone using GlobalScope? We honor system it because we’re small enough, but a lint warning would suffice if we were a larger team

[Rechee Jozil]

@zak.taccardi Yup I meant like GlobalScope. Thanks.

[Rechee Jozil]

so what about if you have multi modules. Should you inject different global scope for each module or share one? thoughts @zak.taccardi @Sinan Kozak?

[zak.taccardi]

share the same global one across

[zak.taccardi]

but, you could decide to break structured concurrency too here

[Sinan Kozak]

We have a ApplicationScope interface in base module and implement that in main application. We pass application scope interface. But i must say it is only for edge cases.