Make relative transition paths work

[saikat]

I saw the issue here remix-run/react-router#1828 and it was closed to continue discussion in this repo. Apologies if this is a dupe or has already been implemented, but I could not find it anywhere.

[taion]

Thanks!

Note that this is slightly different from remix-run/react-router#2172, which I expect to have somewhat different semantics that instead tie into specifics of the router.

I'm not sure where the priority on this one sits, though - a naive implementation of relative transition paths opens a whole can of worms with how the router currently is entirely indifferent to trailing slashes.

[yanivtal]

I'm surprised more people aren't asking for this. It's awfully leaky to have components aware of their absolute paths. Are there other workarounds I'm unaware of or is everyone tightly coupling their routes like an exoskeleton that can never change?

[taion]

Don't they already sort of work when using createBrowserHistory? I don't know that we'll meaningfully resolve this before we figure out the appropriate semantics on the router side, and those are non-trivial.

[yanivtal]

Thanks for the update. I did some more experimentation and I'm getting some weird behavior. When I'm on /base-route and i call history.push('subpath'), the URL updates to /base-route/subpath but nothing happens and I get an error saying 'subpath' doesn't match any routes. Then, if I refresh the page, the route loads properly..

[taion]

I never said the router supported it.

[yanivtal]

Ahh just weird because they punted here in remix-run/react-router#1828 (comment). Guess work's for them?

[taion]

Router discussion is on remix-run/react-router#2172. There's really a number of complexities here.

[yanivtal]

Cool thanks for the right link!