https://angular.io/docs/js/latest/api/router/CanActivate-var.html
https://github.com/angular/angular/issues/4112

On Friday, February 12, 2016 at 7:17:45 PM UTC+1, Andy Macdonald wrote:
>
> Hi,
>
> I'm building an app that needs to redirect to a login view if the user is 
> not authenticated or the verification view if they are registering and need 
> to enter a verification code before getting into the main app!
>
> Once registered they have a dashboard, but if no entries are configured 
> they should be sent to an add screen where they can add new entries.
>
> in beta.0 I was extending RouterOutlet and by checking certain conditions 
> asking the parent router to navigate to the new location.
>
> This worked well until I updated to beta.3 where things have broken and 
> the navigation requests appear to be ignored.
>
>
> Question: Is how I'm doing it the correct way, or is there a more optimum 
> way of handling these decisions?
>
>
> I guess I can set the default url to be the login view and have some logic 
> in it's constructor to navigate to the dashboard if authenticated, likewise 
> I could probably have some logic in the dashboard components constructor to 
> navigate to verification/add new based on logic but this also feels wrong :|
>
> Thoughts?
>

-- 
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 https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.

Reply via email to