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
Currently, if you do router.navigate('foo'), it redirects you relative to that router (as it logical), but there should be some way to tell it to redirect you to foo relative to root. I suggest this can be done in two manners. One, with the options object passed to navigate (something like router.navigate('foo', {useAppRouter: true})), and router.navigate('/foo') where the slash at the beginning indicates I want it to be from the root.
I also think that the useAppRouter should take precedence over the slash start though, so that if you explicitly set useAppRouter: false, and pass in /foo it would still redirect relative to the router. I can't really picture a use-case for it, but I'm sure somebody can, and I don't really see a reason it shouldn't be supported.
The text was updated successfully, but these errors were encountered:
Currently, if you do
router.navigate('foo')
, it redirects you relative to that router (as it logical), but there should be some way to tell it to redirect you tofoo
relative to root. I suggest this can be done in two manners. One, with the options object passed to navigate (something likerouter.navigate('foo', {useAppRouter: true})
), androuter.navigate('/foo')
where the slash at the beginning indicates I want it to be from the root.I also think that the
useAppRouter
should take precedence over the slash start though, so that if you explicitly setuseAppRouter: false
, and pass in/foo
it would still redirect relative to the router. I can't really picture a use-case for it, but I'm sure somebody can, and I don't really see a reason it shouldn't be supported.The text was updated successfully, but these errors were encountered: