-
Notifications
You must be signed in to change notification settings - Fork 59
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
Consider allowing FQN addressing for states w/ parent:
#5
Comments
IMO, I believe that state paths should be agnostic on how they're defined. It should be a common syntax like CSS selectors. I've not reviewed the implementation yet, but I guess that the magic is done based on a convention-based engine against state paths. If this is the case, maybe the solution is to turn paths into something that should be parsed, but internally UI router should store everything based on object properties (i.e. using So I think that above approach would guarantee backwards compatibility while providing more power to handle the whole issue scenario. BTW, any code using Maybe state configuration might define a parameter like |
Revisiting this issue... Did something change about globs and dot notation? |
This issue has been automatically marked as stale because it has not had This does not mean that the issue is invalid. Valid issues Thank you for your contributions. |
angular-ui/ui-router#3119
ui-router/react#11
angular-ui/ui-router#3181
If the state is defined using
parent:
notation, you cannot reference it by including the parents name. For example if a state is declared like this:And you cannot create a sref such as
ui-sref='home.foo'
because home is not technically part of the name of the state.This also affects glob patterns in transition hooks. Is not currently possible to match
foo
using this criteria object:The text was updated successfully, but these errors were encountered: