Changing route during canActivate

[jameskleeh]

Currently, we use the resolve property to return a promise that will need to be resolved before the route changes. It seems like this new router supports that as well which is great! What I haven't seen yet is how we define what we do when the route did not change. The ui-router has the $stateChangeError event, which I am personally not fond of, but it works.

Thanks!

[0x-r4bbit]

Regarding resolve, this might be related: #100

Currently, the router doesn't fire any events. However I actually do think that it should fire events accordingly. @btford you've got an opinion on that?

[tobidelius]

I'm all up for this as well. I use $stateChangeError with ui-router all the time and it would be great if we could have something similar.

[btford]

I think events are kind of a poor API for this. It makes it hard to reason about what's happening in your app, and hard to compose other behaviors.

What I'd rather do is expose a step where you can do arbitrary redirects before any of the other hooks activate. This is essentially a more generalized ".otherwise" block from ngRoute.

[jameskleeh]

@btford How would you envision this use case: I have a service that returns a promise that will either resolve or reject based on whether the user is logged in. I am returning the execution of this service in my "canActivate" function. If it rejects, I want to change the route to say, the login page.

I have precisely that common use case. User opens a bookmark or pastes a URL in the browser to http://acute.com/foo but the associated controller's canActivate function returns false (e.g., user isn't logged in). Calling $router.navigate(some_component) inside canActivate doesn't work.

[jimulle]

I am experiencing this same issue where I cannot use router.navigtate() inside canActivate.

I get an error like:

EXCEPTION: Cannot resolve all parameters for Router(?, ?, ?). Make sure they all have valid type or annotations.

[erashu212]

Hi,

I have to restrict direct access of route if user is not logged in. I have used the @CanActivate for the same but stuck with the further implementation.

Can somebody help me out , how can we navigate to another component inside @CanActivate.

Thanks

[ArniDzhan]

@erashu212 this project is not being supported at the moment, here is updated version of new router with examples. You will be able to use $router.navigate in canActivate to redirect. Or even better have a service which will inject $rootRouter and use .navigate method if auth fails.
https://github.com/petebacondarwin/ng1-component-router-demo