-
-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
notFoundRedirectNamed
issue
#666
Comments
@busslina So you mean the url on top of the browser does not change when notFoundRedirectNamed is ran ? The way i see it is to just update the browser title if tghe notFoundRedirectNamedis used? |
Exactly.
The browser title is working fine. Also, guard redirections also works fine. It's just the case of a not found route. It gets well redirected but it keeps the inexistent url path on the browser address. It's acting like an alias, which could be cool if any want it, but also it must be provided a way to refresh with the actual path. |
For now you can change it yourself... but it needs to be fixed. You can do that before you return it with the notFoundRedirectNamed: ... |
But |
Do you want to change the browsor path without changing the app state ? |
Seems this issue got resolved "by itself". So I'm closing |
This is not a bug, but a bad behaviour IMO.
On a web browser, when routing to an inexistent route, it gets redirected correctly to
notFoundRedirectNamed
, but the browser url got stuck with the wrong route. Is there a way to get it changed to thenotFoundRedirectNamed
value?Thanks
The text was updated successfully, but these errors were encountered: