Skip to content

Koin Annotations 1.3.1 is Out: Streamlining Kotlin Dependency Injection

Koin Annotations 1.3.1

We've just rolled out Koin's latest update with Koin Annotations 1.3.1, bringing with it a few small enhancements and bug fixes. But, stay tuned for the release of Koin Annotations 1.4, bringing new features that will enhance your development experience. Keep an eye out for the upcoming announcement 🔥

What's New?

Update Libraries for 1.3.1

With this update, we've taken the opportunity to bring our libraries up to speed, ensuring that they seamlessly integrate with the latest features and bug fixes in the Kotlin ecosystem. At the same time, we're fully embracing the evolution of the Kotlin language and its tools, with upgrades to Kotlin 1.9.21 and the Google Kotlin Symbol Processing (KSP) tool to version 1.9.21-1.0.16. This dedication to keeping up with the latest advancements in the language enhances Koin Annotations by leveraging the newest language improvements and the advanced capabilities of KSP for powerful metaprogramming and annotation processing.

Safety Issue Fix for SavedStateHandle & Context

A key fix in this release addresses a safety concern related to providing SavedStateHandle and Context. By rectifying this issue, we've fortified the robustness of state management and context handling within Android applications, ensuring that you can confidently manage your application's state without fear of encountering unexpected crashes or behaviors due to context-related issues.


Package Name Default Fix

The update has also brought a refinement in the naming conventions of packages. The correction of package naming to a default scheme enhances the readability and organization of code. This might seem like a minor detail, but it's essential for maintaining a large codebase and ensuring that you can easily navigate and understand the project's structure.

Upgrade to Gradle KTS

The project has embraced the latest advancements in build script technology by upgrading to Gradle Kotlin Script (KTS). This upgrade means scripts are now written in Kotlin, which not only allows for better consistency with the rest of the Kotlin codebase but also takes advantage of the superior tooling support Kotlin provides. This leads to a more expressive and powerful build configuration.