Hmm, that bug is interesting - I definitely had issues with suppressing notify on $state.go in a $stateTransitionStart event, which I didn't quite solve (I ended up approaching the problem from a different direction, the auto-redirecting routes).
e On Mon, Aug 4, 2014 at 12:20 PM, bastienneJS <[email protected]> wrote: > >> You said:"... mainly because I like to have all the calls that would >> influence routing decisions made in the appropriate config block, instead >> of attached to $rootScope with listeners." >> >> Yes the same here. I do not like that a certain state change is handle in >> a global run function and not the appropriate state definitions! Instead I >> have to listen to the $rootScope, baaahhhhh !!! >> > > > I have just read this: https://github.com/angular-ui/ui-router/issues/178 > > It seems when I am inside the stateChangeStart event and I want to do > state.go('putTheSameStateHereWhereICameFrom', 'firstDayOfWeekParameter); > then I run into problems that the ui is not updated... > > sheeezuz... I thought ui-router is out of beta stadium... > > -- > You received this message because you are subscribed to the Google Groups > "AngularJS" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/angular. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
