Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency io.github.hoc081098:solivagant-navigation to v0.5.0 #147

Merged
merged 1 commit into from
Aug 17, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 17, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
io.github.hoc081098:solivagant-navigation 0.4.0 -> 0.5.0 age adoption passing confidence

Release Notes

hoc081098/solivagant (io.github.hoc081098:solivagant-navigation)

v0.5.0

Compare Source

Update dependencies
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.

    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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

| datasource | package                                   | from  | to    |
| ---------- | ----------------------------------------- | ----- | ----- |
| maven      | io.github.hoc081098:solivagant-navigation | 0.4.0 | 0.5.0 |
@renovate renovate bot requested a review from hoc081098 August 17, 2024 18:22
@hoc081098 hoc081098 merged commit 8adbb35 into main Aug 17, 2024
2 checks passed
@hoc081098 hoc081098 deleted the renovate/solivagant branch August 17, 2024 18:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant