$stateChangeStart event is not providing the options

[nielsboogaard]

To check whether the user is authorized for a certain state, i implemented an interceptor which listens to the $stateChangeStart event. After checking the rights, I resume the transition with the following code:

$rootScope.$on('$stateChangeStart', function (event, toState, toParams, fromState, fromParams) {
    //Auth stuff checking here
    $state.go(toState, toParams, {notify: false}).then(() => {
        $rootScope.$broadcast('$stateChangeSuccess', toState, toParams, fromState, fromParams);
    });
});

I notify the stateChangeSucces by hand to prevent endless loops here. The problem is that state.go calls which provides optional options (like reload:true) are not provided by the $stateChangeStart event. This prevents resuming the started transition correctly (because the provided options as originally passed to the state.go method are lost).

Alternative would be to provide a method like $state.resume() which can be used to resume a prevented state transition which takes into account the passed params and options.

[fubupc]

👍

I have the same problem as well.

[OverZealous]

👍 Just caught this trying to figure out #1007

[cbeek]

👍

[RafaelVidaurre]

Same problem here

[sandermak]

+1!

[cbeek]

👍

[mark-veenstra]

+1

[gustavohenke]

+1.
They should be passed to $stateChangeSuccess too.

[flyskyko]

+1

[sebholstein]

+1

[nielsboogaard]

Any updates on this from the angular-ui team? Is there a plan to solve this in a newer version?

[abhinandankothari]

Any Updates on this ? I am facing the same issue

[a14m]

+1

[josephbuchma]

+1

[SinisterLight]

+1

[qpitlove]

👍

[nateabele]

The upcoming release will have new APIs that obviate this.

[karser]

+1

[abhinandankothari]

is this fixed in 0.2.15 ?

[asperling]

👍

[christopherthielen]

I think we can add options as a fifth (!!!) parameter to the $stateChange events. Who has time to make a PR?

[mrtomrichy]

Any news on this?

[thomas3577]

+1

[jeroenlorrentop]

+1

[mambax]

+1

[nateabele]

Any news on this?

@mrtomrichy #1620 (comment)

[zamrokk]

👍