Hello, Kodein community! :wave: I’m wondering, what is your favourite Kodein feature or advantage? W...

# kodein

[Max Kachinkin]

Hello, Kodein community! 👋
I’m wondering, what is your favourite Kodein feature or advantage? Why do you love using it? Especially compared to Koin DI, which is pretty much similar to Kodein in fundamentals and capabilities.

[Max Kachinkin]

For me I can mention ConfigurableDI is pretty handy thing

[ian.shaun.thomas]

Koin error messages leave a lot to desire especially around circular dependency issues. Much prefer using kodein.

[rocketraman]

@Max Kachinkin How do you leverage ConfigurableDI i.e. what use case does it solve?

[Max Kachinkin]

Hey @rocketraman!
My use case is to config (addConfig, addImport) my DI in Android Initializers. It is from androidx.startup package.
Separate Android module can have it’s Initializer and on creating itseft it can add it’s dependencies to DI

[Max Kachinkin]

Something like this

class MyInitializer : Initializer<Unit> {
  override fun create(context: Context) {
    val module = DI.Module("myModule") {
      ...
    }
    ((context as DIAware).di as ConfigurableDI).addImport(module)
  }
}

[Max Kachinkin]

But It has its cost.
Decoupling your code like this it’s even much easier to forget to add binding of something (as we don’t have graph integrity safety)

[Max Kachinkin]

And what is your favorite thing?

[rocketraman]

Ah that would be great for a plug-in type architecture with Set bindings.

[rocketraman]

Not sure I have a favorite. It generally just works. Lots of integration points, customizability, easy and clean to configure (especially with the new function recently added, inspired by Koin), Seems relatively performant at startup time, though I wonder if KSP could help improve this even more in the future by moving some runtime init to compile time.

[Max Kachinkin]

Oh, I found this new API that you suggested earlier! Thanks for this!) Yesterday I simplified my bindings with it.

[Max Kachinkin]

I even wrapped it with own wrappers 🙂
So instead of this:

bind<Repository>() with singleton { new(::RepositoryImpl) }

I write this:

bind<Repository>() with singletonOf(::RepositoryImpl)