Consider allowing FQN addressing for states w/ `parent:` about core

[mfidemraizer]

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 parent).

So I think that above approach would guarantee backwards compatibility while providing more power to handle the whole issue scenario. BTW, any code using parent instead of a path would be broken.

Maybe state configuration might define a parameter like legacy defaulting to true... And/or a service parameter also called legacy to define what should be the default value to legacy if each state doesn't provide it explicitly...

[cadilhac]

Revisiting this issue... Did something change about globs and dot notation?

[stale]

This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs.

This does not mean that the issue is invalid. Valid issues
may be reopened.

Thank you for your contributions.