This repository was archived by the owner on Apr 8, 2026. It is now read-only.
Having a route that has no history #61
Unanswered
gentledepp
asked this question in
Q&A
Replies: 2 comments 7 replies
|
@OmidID I guess my problem here is that I do not understand what the difference is between the navigationtypes: Could you please add documentation to the readme.md? 😇 |
1 reply
|
Thank you so much for the answer. Also I do not know how to implement the login page now. Because it should not be kept on the navigatesrack. But I do not want to use Replace root since I want to keep the navigation history as such 🤔 Can I use "Modal" even if a page is not within some host? |
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment



Uh oh!
There was an error while loading. Please reload this page.
Hi!
I went through the different navigation types, but could not find anything suitable.
Basically what we have is some route "authenticate" that can be called from any other route.
It is shown when the user has to login again (maybe the refresh-token was invalid or something)
Once logged in, I do not want to be able to "navigate back" to that view.
So I need a route that can be shown, but once the user leaves that page, does not create a history entry (speaking in browser language)
Is there any way I can achieve that?
Thanks!
All reactions