-
Notifications
You must be signed in to change notification settings - Fork 210
$state.go onEnter resolve two times #138
Comments
confirmed, thanks for the bug report |
note to self:
|
@Pirfox here's a workaround which effectively disables future states' resync code. I assume you're not using future states?
|
@christopherthielen Yeah i am not using future states. I will try your proposal in a few days when i am at work. Thank you :) |
So i am back at work and i could try your solution, it makes the resolve and everything else only once but it disables my |
Temporary fix for christopherthielen#138
I don't have time to fix this before 0.0.12. However, 0.0.12 has a modular build, so if you are not using future states, you don't have to include that code. |
I have a problem when using $state.go in the onEnter fonction with direct acces to the state via URL, after the redirection eveything is done again. I tried without the lib 'ct-ui-router-extra' and the behavior is gone and it works fine.
To reproduce http://plnkr.co/edit/DjcfKydwRm159sb90xdn
And go to http://run.plnkr.co/7pT8SD2nnQvlrALn/#/top/detail
Everything will be done two times and i don't see why, so if you have any idea how this happens?
Expected output:
After the two resolves i have what i want, but this is a performance hit when i work on huge list etc
The text was updated successfully, but these errors were encountered: