$routeChangeSuccess is fired before route has been resolved
Opened this issue · 1 comments
yeraycaballero commented
It seems $routeChangeSuccess is fired before is supposed to. Basically is not waiting for resolving $routeProvider.resolve hash of promises. I have prepared a plunker http://plnkr.co/edit/Hvqejt that reproduces it
Current code follows this order
- $routeChangeStart
- $routeChangeSuccess
- route is resolved
whereas it should be
- $routeChangeStart
- route is resolved
- $routeChangeSuccess
krystiangw commented
👍