You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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 canGoBack though I'm not quite sure it'd fit into the current API well. Guess it can just go on the route location context if need be.
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: