Feature - Ability for client to detect or respond to redirects

[Rican7]

Describe the problem

From what I can tell, there's no way to reliably detect a redirect in client application code.

Describe the proposed solution

Ideally there'd be a way to detect a redirect, either as a hook or maybe even as a piece of the data included in the Navigation type.

Alternatives considered

I looked to see if this data was available in the navigating type from $app/state, checked to see if it was available in client hooks, and tried to see if I could just use document.referrer, to no avail.

Importance

would make my life easier

Additional Information

No response

[dummdidumm]

What's the use case?

[Rican7]

What's the use case?

My app does some overriding of link clicks to go back in the history stack if you're returning to a certain part of the app, to behave much more like a native Android app with a back stack, this all works pretty well through listening on $app/state/navigating state changes, but currently falls apart with redirects.

[Rican7]

This wouldn't exactly be necessary if #5478 was implemented, and therefore is related.

[gregg-cbs]

The use of the "redirect()" and "error()" methods client side would be very helpful.

[cellulosa]

What's the use case?

I would use it to check if a user is logged in, and if not redirect to the login page. I have no server as the app runs via capacitor in ios.