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

Add replace option for .navigate() and .open() events #32

Closed
Tracked by #31
igorkamyshev opened this issue Aug 20, 2022 · 1 comment
Closed
Tracked by #31

Add replace option for .navigate() and .open() events #32

igorkamyshev opened this issue Aug 20, 2022 · 1 comment
Labels
enhancement Improvement of existing functionality
Milestone

Comments

@igorkamyshev
Copy link
Contributor

igorkamyshev commented Aug 20, 2022

Now .navigate and .open events push new state, in some cases it would be necessary to replace current state to prevent user from going back.

@sergeysova sergeysova added this to the v1 milestone Aug 20, 2022
@sergeysova sergeysova added the enhancement Improvement of existing functionality label Aug 20, 2022
@sergeysova sergeysova changed the title Replace in navigate and open Add replace option for .navigate() and .open() events Aug 20, 2022
@Kelin2025
Copy link
Collaborator

Kelin2025 commented Sep 10, 2022

Added in v0.6.3 (PR #34)

someRoute.navigate({ params, query, replace: true })

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvement of existing functionality
Projects
None yet
Development

No branches or pull requests

3 participants