Closed smithc42 closed 10 months ago
This is quite a large refactor of the code. I can see that keeping all dependencies in one place is helpful but I would like to understand how updating/working with this help. Currently Android studio understand that the dependencies are dependencies and offers updates to recent version via quick fix popup. I assume that will be lost if I merge this PR. Is there a good way to check for oudated dependencies with your libs.versio.toml
?
Looks like Android Studio actually understand the lib.version.tol.
I noticed different versions of Kotlin defined in the build files (
1.6.21
/1.7.22
/1.9.0
) so I decided to consolidate and align project dependencies through the use of gradle dependency catalog which acts as the source of truth for versions. This should allow for easier addition and management of existing and new dependencies going forward.