Hey everybody, I've released version 6.0.0 of Kode...

# kodein

[salomonbrys]

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

[dave08]

Are there docs for Android yet? Is closestKodein still needed?

[salomonbrys]

The API hasn't changed much: http://kodein.org/Kodein-DI/?6.0/android

[dave08]

I thought with the new scopes, the api would be standardized... it's less confusing.

[salomonbrys]

@dave08 closestKodein is not about scopes. Why do you think it's confusing ?

[dave08]

Because it only exists in Android... and I know the idea is to get the parent scope.. but since there's no such concept in the main version, it's a bit hard to grasp what is really goong on and how it fits into the picture. It would be nice to have one set of consistent and easy to use concepts for everything... @salomonbrys

[dave08]

I'm sure this might have use cases elsewhere, no?

[salomonbrys]

Well, in future frameworks, yeah. But not in core Kodein...