I ended up doing something like that, but I doubt it's the idiomatic way…

class BatteryBroadcastReceiver : KodeinAware, BroadcastReceiver() {

    override lateinit var kodein: Kodein

    private val myBinding: Stuff by instance()

    override fun onReceive(context: Context?, intent: Intent?) {
        if (!::kodein.isInitialized) {
            kodein = (context as KodeinAware).kodein
        }
        ...
    }
}

So... here we go! ANNOUNCING KODEIN-DI 5.0.0!!! First of all, some acknowledgments: - Huuuuge thank you to @olonho and his amazing team of Kotlin/Native. For creating the technology of course, but also for being ultra-reactive! Most of the bugs & crashes that I reported were fixed within 72 hours. Some missing pieces were prioritized to allow Kodein 5.0 to be compatible with Kotlin/Native. I have never worked with such a great team and it has been an honor to contribute, as little as I did, to this great endeavour! - Great thanks to all of you who annimate this channel while I'm away. I've never been a social community guy, and it is because you answer here on Slack as well as on other medium that this community lives and this library finds it audience. So thank you to @Andreas Sinz, @streetsofboston, @jdorleans, @kailan, @dave08 and everyone that I forgot to mention here 😉 - Thanks to all of you who come with new ideas. 80% of Kodein-DI's features are because of your dissatisfaction in the current state of Kodein. Features such as subtype bindings, argument uptype handling, multiton, all matching retrieval, set binding, and much more are included because someone came and ask "How can I do that?" Now, for the annoucements themselves. First and foremost, Kodein-DI 5.0.0 stable is live in JCenter. It took some time because of a bug in JCenter (only half the packages were released). There are two main differences from the previous beta 5 version: - The packages have changed again (sorry about that): they are now inside

org.kodein.di.*

- Introducing subtype bindings, which allow to register a parent type and the a binding factory that will provide a binding for each new subtype of this parent type. As usual, everything is in the documentation (http://kodein.org/Kodein-DI/) and changelog (https://github.com/Kodein-Framework/Kodein-DI/blob/master/CHANGELOG.md). Second, announcing the Kodein Framework (http://kodein.org). It does really not exist yet: Kodein-DI is (at the moment) the only released component of the framework. This framework will propose various components that are focused on multi-plateform development (JVM/Android/JS/Native/iOS). Note that each component will be usable by its own and that Kodein-DI, as well as other components, will continue to also be focused on the JVM and Android. Being multi-platform does NOT mean sacrificing JVM only goodies. Kodein-DI 5 includes multiple features that are available only to JVM & Android, and those features will continue to be supported. Some components of the framework (such as Kodein-JSON) will be focused exclusively on multi-platform and some other (such as Kodein-DI) won't. The choice is made based on the usefulness of the component outside of the multi-platform ecosystem. The framework itself will aim to provide a full ecosystem to easily create business code, modules and architecture to be shared between platforms. In term, applications that are developed with the Kodein Framework should contain 60% to 80% of shared code between platforms. Finally, to support all of that, I'm very happy to announce the Kodein company: http://kodein.net . This company, based in France but active in all Europe, develops three major axes: - Kotlin consultancy & development services. - Kotlin training & migration programs. - Kodein framework development & support. If you would like to work or contract with us, feel free to contact me at salomon@kodein.net. Note that the Kodein framework in general and the Kodein-DI library in particular will remain fully Open-Source and that the community will continue to be supported. I am Open-Source at heart and the company we are building is too. We plan to monetize through services: consultancy, SLA support, training, development, etc. All of this is still in early stages. In the meantime, I hope you enjoy Kodein-DI 5.0.0 😉 Salomon.

@salomonbrys What do you think of this reddit? https://www.reddit.com/r/androiddev/comments/8ch4cg/dagger2_vs_koin_for_dependency_injection/dxf4o08/?context=2

@salomonbrys Can one imported

Kodein.Module

access the bindings in another imported module, or only the importing

Kodein

has access to all the module's bindings? If the latter then a module will have to be a

fun

that accepts all dependencies needed from other modules, or does it also have to import the module to use it...?

Do I have to use interfaces for my services? I strongly disagree with this line from the Kodein docs:

In DI, each business unit will have dependencies. Those dependencies should (nearly almost) always be interfaces.

So I am wondering if Kodein is a good choice for me if I don't have silly interfaces for every single dependency.

Kodein 4.1 What am I doing wrong/forgetting here? I have a concrete class

class Foo(view:ViewFoo)

And a Kodein.Lazy with this binding

bind<Foo>() with scopedSingleton(androidFragmentScope) {
            Foo(it)
        }

and on my `MyFragment(), ViewFoo`I’m retrieving like this

val foo by kodein.with(this).instance<Foo>()

But then it throws this error

No factory found for bind<Foo>() with ? { MyFragment -> ? }
  
Registered in Kodein:
   bind<Foo>() with scopedSingleton(androidFragmentScope) { Fragment -> Foo }

@hide You need to create a new Kodein instance:

override val kodein = Kodein.lazy {
    extend(closestKodein())
    import(menuViewModelModule(this@MenuFragment))
}

I ran into a similar problem when I first discovered about scopes. Here, inside your activity, your kodein scope is not defined, meaning that your

viewModel: MainViewModel by kodein.instance()

will try to retrieve an unscoped MainViewModel (and none are defined in your bindings!)

Either use

val myInstanceOfT by kodin.instance<T>(tag)

or

val myInstanceOfT = kodein.direct.instance<T>(tag)

Has anyone tried testing a kodein project with travis? My tests run fine (gradle test), but on travis I get null pointers when calling kodein.instance()

Is there a way to get an instance if you only have a Java or Kotlin class but can't supply a reified type?

@salomonbrys I have:

bind<ProgressNotifier>() with factory { id: Int, iconRes: Int, title: String ->
        ProgressNotifierImpl(instance(), id, iconRes, title)
    }

    bind() from singleton { InstallationNotifier(factory() as ((Int,Int,String) -> ProgressNotifier)) }

But idea tells me that type inference failed for

A

on

factory()

call in the

InstallationNotifier

constructor... how could I acheive this? the constructor takes:

val progressNotifierFactory: (id: Int, iconRes: Int, title: String) -> ProgressNotifier

@salomonbrys Thanks for reporting that issue! Let us know how you work around this issue.

Does kodein support injecting platform specific objects into multiplatform common code?

Hi guys, I posted a question on StackOverflow regarding managing the lifecycle of Kodein context/container. Would be great if you guys have some thoughts on it. Thanks. https://stackoverflow.com/questions/50973181/shutting-down-closing-kodein-context

@salomonbrys In v4 there was a way to specify a provider for an argument for a scope (https://github.com/Kodein-Framework/Kodein-DI/blob/4.1/shared/erased/kotlin/com/github/salomonbrys/kodein/erased/EInjected.kt#L169). This was helpful when injecting a value from a scope in a class where the scope argument wasn't ready at initialization (e.g. a Fragment that needed something from an Activity scope to be injected). Is there any way to do something similar in v5 with contexts?

abstract class MyFragment: Fragment, KodeinAware {
  private val parentKodein: Kodein by closestKodein()

  override val kodein = Kodein {
  }

  // contrived example, but whatever
  // doesn't work because activity is null
  private val presenter: MyActivityPresenter by on(context = activity).instance()

  // used to be able to do:
  // private val presenter: MyActivityPresenter by with { activity }.instance()
}

Hi all, I'm new to Kodein, and relatively new to Kotlin. I saw one can get all instances by calling

kodein.allInstances

, is there a way to find them by name? I'm a 14 yr old Spring user, so I'm kinda used to that 😉

Does Kodein have any workarounds for the lack of Kotlin support for SAM conversion on Kotlin interfaces? I want to define a simple function-based injection but the type signature isn't enough to avoid ambiguity, so it seems either tags or an interface is required. I prefer the interface, but with no SAM conversion the binding becomes messy.

Hi guys! Is Kodein have future plan to verify dependencies graph at compile time?(same as dagger2) or can you suggest any alternative solution to do something like that in Kodein?

@judrummer yes, thats fine. Maybe Kodein could provide a method that you can call inside a unit-test that tries to retrieve instances of every bound Type. What would you say @salomonbrys?

Hi! I've been working on a Kodein course mostly thought for Android apps and based on nested scopes (+testing). It'll be completely free during a whole week. Please don't hesitate to give feedback. You'll probably like it @salomonbrys. I'd love to get some feedback from you 😊 https://twitter.com/JorgeCastilloPr/status/1030486221091491840?s=19

@salomonbrys is it not advised to bind function types? I have a binding for

(Long) -> String

, but when I inject it, I get a

(String) -> Request)

which is obviously not good.

So, here we are. Just in time for KotlinConf, Kodein-DI 5.3.0 has been released 🙂 It features: - A few bugfixes for Android - New Kotlin/Native plugin usage - Non-synced singletons & multitons (http://kodein.org/Kodein-DI/?5.3/core#_non_synced_singleton) Also Kodein-DI now has: - a new logo - a new website : https://kodein.org/di/ Finally: Kodein Koders, the company that I created to develop & support the Kodein Framework is partner at the KotlinConf. Please do come by to say hello if you happen to be in Amsterdam thursday or friday.

Hi @streetsofboston The pleasure was mine 🙂 So, this really depends on the

AppSessionScope

and

UserSessionScope

implementation. I suppose they are using

MultiItemObjectRegistry

? There's a

clean

method on it, to "clear" the registry, which makes all objects go out of scope. However, this might not be necessary if the registry is only "held" by an object that goes out of scope. GC can take care of that. Using a

WeakContextScope

can also be a way to not manually clean the registry.

Is there a way to know if there are unused dependencies in Kodein-DI? It's a big more difficult when everything is

instance()

and

factory()

in the bindings... it greatly reduces typing but sometimes leaves dangling dependencies...

Hey everybody, I've released version 6.0.0 of Kodein. Note that It is NOT available on JCenter yet, due to sync issues. I've contacted JFrog to work the issue. So, in order to use it, you need to manually add Kodein-DI repository : https://bintray.com/kodein-framework/Kodein-DI. I'll post here once the issue is resolved and Kodein-DI 6.0.0 is in JCenter. So, what's new in this version? - As promised, it is built with Kotlin/Native 1.0.1, so it is fully compatible with Kotlin/Multiplatform projects. - If you want to use Gradle Metadata 0.4 (Gradle 4.8+), you can: use version 6.0.0-LGM in the dedicated repo (will NOT be synced to JCenter, so you always need to add it manually): https://bintray.com/kodein-framework/Kodein-DI-LGM - Scopes were too complicated in Kodein 5.x, this release entirely rethinks the

Scope

interface, so it is much (much) more easier to create your own scopes. More in the doc: http://kodein.org/Kodein-DI/?6.0/core#scope-creation Of course, the changelog is here: https://github.com/Kodein-Framework/Kodein-DI/blob/6.0/CHANGELOG.md Also, if you want to see what's in my mind for the future, you can do so here: https://github.com/Kodein-Framework/Kodein-DI/blob/6.0/TODO.md Finally, please note that due to this sync issue with JCenter, I haven't updated master yet. The default documentation is therefore still showing Kodein 5.3. The updated documentation for version 6.0.0 is here: http://kodein.org/Kodein-DI/?6.0

@salomonbrys Hi, Is Kodein support multiplatform project already? I didn't see kodein common module in document. Do I need to import all of this (https://github.com/Kodein-Framework/Kodein-DI/tree/master/core) in correct multiplatform sourceSet?

Hey, I don't suppose anyone could help me out with this issue: https://stackoverflow.com/questions/53408628/how-can-i-create-di-bindings-for-generic-types-in-kotlin TL;DR: need to be able to register

Foo<T>

and resolve

Foo<Int>

or

Foo<String>

.

Hey I have issue with Kodein versioning. Github newest version is

5.3.0

while all docs are referring to

6.0.0

.

5.3.0

works fine. When I try to use

6.0.0

dependencies are resolved properly but some of the stuff is missing eg.

KodeinAware

interface. should I stick with

5.3.0

or I should use

6.0.0

and do something differently? My dependencies

import "org.kodein.di:kodein-di-generic-jvm:5.3.0"
import "org.kodein.di:kodein-di-framework-android-x:5.3.0"