appyx
appyx copied to clipboard
Model-driven navigation + UI components with gesture control for Compose Multiplatform
think about how we can avoid keeping unnecessary object after state initialization
Make it BaseNavModel test
Test different child lifecycle combinations (except ones MinimumCombinedLifecycle already tested)
Hello, it is a question more than a bug, is there an example of integration with hilt or dagger 2?
For all published modules: - Use `org.jetbrains.kotlinx:binary-compatibility-validator` and add it as part of CI workflow - Use `explicitApi()` mode for Kotlin Gradle plugin
And provide as `LocalComposition`. See https://github.com/badoo/RIBs/pull/374 By using `SavedStateRegistry` per node we are scoping instance saving to a particular place instead of relying on Activity. JetPack navigation does the same.
There are quite a few libraries in the project that are out of date. Rather than having to remember to check these occasionally (and potentially wait months), we should investigate...
We could introduce some simple dagger hilt integration to make it easier to share node factories across modules without exposing internal dependencies.