$state.go with notify: false option error

[k-one-o-two]

I've got a controller ListCtrl and there is something like
$state.go($state.current.name, {page: $scope.currentPage}, {reload: false, notify: false}); (used for the pagination).
The problem is that ListCtrl controller is being called after changing the state to another (i.e. not $state.current).

Changing notify to true fixes an issue, but destroys my pagination logic.

I've found a temporary solution: set some var on $stateChangeStart to true and to false on $stateChangeSuccess, then use in a controller like $rootScope.stateChanging || init();. It works but seems strange to me.

Is there something I'm doing wrong or it's a bug?

[j1nX1988]

+1

[dougarp]

+1

[christopherthielen]

notify: false has so many side effects that it is deprecated. We're replacing the functionality with something called dynamic parameters for final 1.0 release.

I apologize, but we're not going to be addressing any notify: false issues in 0.2.x

To be clear, notify: false only claims to do one thing: suppresses the $stateChange* events. The rest is "up to you". I highly recommend avoiding it.

[Etheryte]

See #1758