-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Ability to route "back" #58
Comments
I don't think it's on our todo lists but would be happy to see it supported if you did want to give it a shot! I'm not against a |
Ok great, I will take a look at the source code and have a go at implementing just the back functionality first! |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
It's a shame the Navigation API is still a couple years out, required no more lib code to support forward & back nav: e018443 |
I've rolled my own router for a while but would like to move to using this package. I went to migrate one of my existing apps and realised that I use
router.back()
quite prolifically in the app with my hand rolled router implementation.Do you ever plan to support this operation at all?
If so that is great and I could even look at adding this functionality via a PR.. it might be also be worth including a
canGoBack
field like in expo router which detects whether there is a previous route in the navigation history stack.The text was updated successfully, but these errors were encountered: