-
Notifications
You must be signed in to change notification settings - Fork 3k
$urlRouterProvider.otherwise issue #1351
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
Comments
Hi, sorry this is not currently supported. We are considering adding "default child substate of an abstract state" (#1235), but it is not currently implemented. The FAQ entry regarding a child substate with url "" is a workaround, but it has issues, such as no ui-sref capability. Stay tuned to #1235. I think it will be a few releases off, unfortunately. |
Can you please elaborate what exactly is not supported? This behaviour seems to be a bug. In my plnkr, when I try to invoke child state ('abstractBaz.bar') of an abstract state ('abstractBaz'), "otherwise" redirects me to '/foo'. This is what I consider incorrect. |
@Inkp I definitely misunderstood what your plunk was trying to do. I thought you were trying to navigate to the abstract state. Here's what's happening:
You should either put your URL on the child state
or give the bar state an empty url so the url rules will match
|
@christopherthielen, unfortunately, I cannot implement neither one of your suggestions, because I am using {params: []} in my child states. The only viable option I see is to make parent state non-abstract and to redirect to one of the children on the parent state direct activation. |
+1 on supporting this feature |
It seems, that otherwise() triggers redirect on invoking child state of an abstract state.
See: http://plnkr.co/edit/UHzkSIBlYVQ0jaYcUTki?p=preview
The text was updated successfully, but these errors were encountered: