Resolver's order of execution

[maharaja-sv]

I added resolver in both child state and parent state. When I accessed my child state directly the order of resolver is executed in reverse. First the child state resolver executes then parent state resolver executes, which must b executed in reverse. For ex. Consider there are countries List from which I select state then city, I need to get countries List(COUNTRY State) through my parent resolver and then state list(STATE State) for a specified country through next child resolver which has Country as $stateparam and then city list(CITY State) for the selected state through next child resolver which has state as $stateparam. Now when I access the url with country and state directly i.e /India/TamilNadu then my resolver is executed in reverse.

[timkindberg]

Will need a plunkr to look at. Thanks.

[frapontillo]

I wasn't sure if this was by design or an issue, so I opened a question on StackOverflow.
You can look at a working plnkr detailing the problem here.

This might also be related to #868.

[rschmukler]

@timkindberg any update on this / #868 ? I realize it's an old issue, but this would still be great!

[eddiemonge]

https://gist.github.com/eddiemonge/f6a58169c2846731a1eb