Something I’m missing now and have to write on my ...

# kodein

[Marc Knaup]

Something I’m missing now and have to write on my own.
A scoped builder 🙂

val kodein = Kodein.scoped(myScope) {
   bind() from singleton { context.createFoo() }
}

If there is already a way that would be great!
If you think it’s worth adding I’ll open an issue.

[romainbsl]

If I understand what you are looking for, is a way of scoping everything onto the same scope once?

[Marc Knaup]

Yes. So I can have my own DSL that just takes Kodein.ScopedBuilder<T>. () -> Unit for example.
No need for “consumers” to know about how scoping is implemented.

[Marc Knaup]

But I’m thinking about eventually wrapping the entire Kodein DSL now anyway 😄

[romainbsl]

Indeed we already had though about it, but didn’t find the time to implement such a thing. PR are welcome anyway 🙂. Otherwise fill-in an issue, and we should jump on it as soon as we are done with hot stuffs …

[Marc Knaup]

Cool!
What’s the hot stuff right now? 🙂

[romainbsl]

Moving the whole API… from Kodein to DI as we will soon have more Kodein libraries, so the class name Kodein won’t fit anymore.

[Marc Knaup]

👌

[romainbsl]

+ rewamping the type management to bring more safety

[Marc Knaup]

Including using typeOf()?

[romainbsl]

+ KMP stuff like a nice API for Swift etc

[romainbsl]

yep, using typeOf() for anything but JVM, as its not fully compatible yet

[romainbsl]

+ that will allow us to deprecate libs like generic-jvm / erased to the benefit of one unique KMP lib

[Marc Knaup]

yeah wohoo 🙂
It’s so annoying always having to import both packages

[romainbsl]

7.0 its just around the corner. Unfortunately we had to broke some API compatibility because of the renaming 😢

[Marc Knaup]

Move fast an break things!

I guess you still won’t come even close to how much Kotlin is breaking with almost every update 😉

[Marc Knaup]

(although that’s mostly bugs)