Closed renovate[bot] closed 3 months ago
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 2.60%. Comparing base (
71b47ff
) to head (f466c76
). Report is 1 commits behind head on master.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
This PR contains the following updates:
0.4.0
->0.5.0
Release Notes
hoc081098/solivagant (io.github.hoc081098:solivagant-navigation)
### [`v0.5.0`](https://togithub.com/hoc081098/solivagant/blob/HEAD/CHANGELOG.md#050---Aug-17-2024) [Compare Source](https://togithub.com/hoc081098/solivagant/compare/0.4.0...0.5.0) ##### Update dependencies - [KotlinX Coroutines `1.9.0-RC.2`](https://togithub.com/Kotlin/kotlinx.coroutines/releases/tag/1.9.0-RC.2). - [AndroidX Lifecycle `2.8.4`](https://developer.android.com/jetpack/androidx/releases/lifecycle#2.8.4). - [AndroidX Compose Activity `1.9.1`](https://developer.android.com/jetpack/androidx/releases/activity#1.9.1). - [AndroidX Annotation `1.8.2`](https://developer.android.com/jetpack/androidx/releases/annotation#1.8.2). ##### Added - **StackValidationMode**: Introduced a new sealed interface `StackValidationMode` to handle different stack validation modes in the navigation stack. This interface includes three implementations: - `Strict`: Ensures the stack is always in a valid state and throws an exception if it transitions to an invalid state. - `Lenient`: Ensures the stack is always in a valid state but takes no action if it transitions to an invalid state. - `Warning`: Ensures the stack is always in a valid state and logs a warning if it transitions to an invalid state. - **NavHost**: Added a new parameter `stackValidationMode: StackValidationMode` to the `NavHost` composable. Default value is `StackValidationMode.Lenient`. ```kotlin NavHost( startRoute = LoginScreenRoute, destinations = AllDestinations, navEventNavigator = navigator, destinationChangedCallback = { currentRoute = it }, stackValidationMode = StackValidationMode.Warning.Debug, // <--- Set the stack validation mode ) ``` ##### Fixed - `Lifecycle*Effect` completion is now idempotent (i.e., if the `onStopOrDispose` was called because of the Lifecycle being stopped, it won’t be called a second time upon disposal unless the Lifecycle goes back up to `STARTED` again).Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.