Ability to route "back"

[lukejacksonn]

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.

[rschristian]

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.

[lukejacksonn]

Ok great, I will take a look at the source code and have a go at implementing just the back functionality first!

[Jeremboo]

Hi there,

After navigating through multiple pages, it seems I can only push back once.
Could this be the same issue, or should the native history behavior be working as expected?

[rschristian]

How are you "pushing" back? history.back() seems to work okay for most cases but it isn't integrated into the router (as this issue notes) so could be problematic.

[Jeremboo]

I'm using the standard navigation method the 'back' arrow button. But both it and history.back() trigger the popstate event. So I assume they both have the same behavior.

Which is, after using it once, the button becomes disabled, even though the history length is greater than three.

[rschristian]

Sorry, can't reproduce. Seems to work just fine for me.

Ex: https://github.com/rschristian/demo__iso-back-nav

Click through links in the header, hit the button or browser "back" button to got back.

Edit: You're not using the replace param on the route() function, right? I.e., route('/foo', true)?

[Jeremboo]

Alright my bad...
I was experimenting with my forked version and looks like my changes unintentionally broke the history behavior.
Sorry for the waste of time.

[rschristian]

No worries, we might be missing a test or two here that can help confirm the behavior is working as expected.

[mike-lischke]

Navigating through the history works fine as long as you don't touch a page (component) with a nested router. Once this happens the history starts behaving pretty erratic. Hard to predict where you end up. I don't replace history entries in route() calls, nor do I use a custom history.

[rschristian]

@mike-lischke That's not related to this issue, please open a new issue with a minimal repro instead.

[rschristian]

It's a shame the Navigation API is still a couple years out, required no more lib code to support forward & back nav: e018443