Prior to version 0.10 we've used nested <Routes> to (lazily) apply additional routes for customer-specific sections of our apps.
The recommendation from 0.10 onwards was to use nested <Router> with appropriate base properties. The seem to be issues with this approach.
I've put together a stackblitz example in an attempt to provide a concise example for exploring the various issues:
- Nested router home page not rendering on first navigation (only on refresh).
- Nested router's other routes not rendering ever.
<A> links get offset from nearest nested router - but need to be able to router globally within the app (outside the nested router).- The root router seems to be handling all anchor clicks so the nested router never gets a shot at them.
Open the stackblitz example and follow the notes on each page. Preview in a new tab to better see the url.
Supporting additional routes loaded more deeply/lazily within the app is a valid use-case. Is it possible to continue supporting that somehow?
Other likely related issues:
#334
#255
Prior to version 0.10 we've used nested
<Routes>to (lazily) apply additional routes for customer-specific sections of our apps.The recommendation from 0.10 onwards was to use nested
<Router>with appropriatebaseproperties. The seem to be issues with this approach.I've put together a stackblitz example in an attempt to provide a concise example for exploring the various issues:
<A>links get offset from nearest nested router - but need to be able to router globally within the app (outside the nested router).Open the stackblitz example and follow the notes on each page. Preview in a new tab to better see the url.
Supporting additional routes loaded more deeply/lazily within the app is a valid use-case. Is it possible to continue supporting that somehow?
Other likely related issues:
#334
#255