:wave: is anyone using decompose alongside somethi...

# decompose

[Marc]

👋 is anyone using decompose alongside something like koin or kodein?

[Arkadii Ivanov]

A few days ago I had an experience of integrating Decompose into a multiplatform project - the official DroidconKotlin app. The project already uses Koin for DI. I'm not sure yet whether my PR is going to be merged or not, but you can check the branch - https://github.com/touchlab/DroidconKotlin/pull/165

[Marc]

do you use scopes for anything?

[Arkadii Ivanov]

I don't think so. DI was already there, I didn't notice any scopes.

[Marc]

thanks!

[Adam Brown]

I'm using it with Koin

[Adam Brown]

I don't use scopes

[Andrew Steinmetz]

I'm using it with Kodein in my own app and can't say that I have needed to use scopes as decompose will generally manage the scope of the dependency since it manages lifecycles

[Marc]

i was thinking the same thing, so you are just making everything UI related a provider/factory and then let the LifecycleAware class handle the lifecycle etc right?

[Marc]

i guess if one really wants kodein to manage everything through scopes something like this would be trivial to implement. but as you said it’s probably not needed.

[Andrew Steinmetz]

Yup, pretty much only using it for singleton and factories and inject everything through the constructor (technically could do the same thing with koin) and let decompose manage the lifecycle. So a sample would just look like:

class FooBlocImpl(
    componentContext: ComponentContext, 
    private val bar: Bar,
    //
) : FooBloc, ComponentContext by componentContext {
    constructor(context: ComponentContext, di: DI) : this(
        componentContext = context, 
        bar = di.direct.instance() 
    )
}

So if FooBlocImpl is being added to the stack, all the necessary dependencies are created and decompose will not recreate another instance unless it was completely removed off the stack and pushed back on. Even the instance in my bottom navigation bloc, it uses the bringToFront() navigation method which will either create a new instance or bring a current one on the backstack to the front preventing it from creating multiple instances of the FooBlocImpl.

I have considered moving to something like kotlin-inject using assisted injection for the ComponentContext of child blocs just for the compile time safety. Haven't really faced many problems with kodein though. In sample apps I have made, its also pretty easy to create your own DI service locator just using the basic language constructs in the kotlin language. Kodein and koin just solve a lot of problems that arise in more complicated DI setups.

object DI {
    val foo = Foo() // eager singleton
    val bar by lazy { Bar() } // lazy singleton
    val authUseCase: AuthUseCase // factory 
        get() = AuthUseCaseImpl(foo)
    val createFizzUseCase(id: String): FizzUseCase = //assisted injection
      FizzUseCaseImpl(id, bar)
}