This repository was archived by the owner on Jul 17, 2024. It is now read-only.
Repository navigation
Releases
Releases · Nek-12/AndroidUtils
2.0.0 : Library deprecated
🛑 Since 2.0, this library has been integrated into KMPUtils.
This repository is no longer maintained
Not everything was migrated, namely room, preferences and view extensions.
Please copy and paste those into your project if you are still using them and do not wish to migrate to a more modern stack.
1.1.3
1.1.2
1.1.1
1.1.0
- Update dependencies to latest (Kotlin 1.9.10, compose 1.5.4)
- Update minSdk to 24 and targetSDK to 34
- Added about 20 new extension functions, mainly for Compose
- Removed databinding completely
- Remove coroutines-ktx functions that are already included in the KMPUtils repository
- Fixed some issues with withApiLevel & other functions
1.0.4: Downgrade versions to stable, up compose to 1.4
What's Changed
Full Changelog: 1.0.3...1.0.4
1.0.3: Fixed core-ktx targeting Android 14
1.0.2: Deprecated databinding, fixed, deps update
What's Changed
Full Changelog: 1.0.1...1.0.2
1.0.1
1.0.0: Migration to KMMUtils
This is a release that starts the migration process to KMMUtils - a new repository hosted under Respawn organization that will be the successor to this one.
Respawn Team and me personally are adopting KMM wherever possible, since KMM is now in Beta and on its way to stable.
Breaking Changes:
- Removed core-ktx entirely. CoreKtx has been preserved and split in the KMMUtils repository. Most notably, ApiResult has been migrated there with major improvements to the library. See the upcoming documentation in the repository to know what's new.
- Fixed screenWidth in compose
- Added withDensity extension in compose because using with(Density) was annoying as hell
- Provided a String.isValid to android module that duplicates functionality of core-ktx for time being because it was used there
- Moved some coroutine-ktx functions to KMMUtils coroutines module
- Deprecated Text class. Yes, it's true. Throughout our experience, we found out that our usage of the Text class led to many violations of Clean Arch and SoC principles, making UI code (resolving string) leak into the Domain/Data layers and business logic. The suggested approach is now to use some other kind of identifier for your strings, or at least use resource ids. You should really resolve strings on UI layer only. It's possible we will be bringing Text class back to KMMUtils in some other form as we figure out how to adapt it to K/N without breaking SOLID in the process.
- Updated deps, most notably compose 1.4-alpha05, Kotlin 1.8.0 and KSP 1.0.9, along with Gradle 8.0