Hi Rafa, I have done a load f angular apps, and usually, you don't need a run statement at all. In your case, you can encapsulate the login in its services, and summon the one you need on instantiation of the top component for the part you are activating. There is no issue there, and you can maintain as many login-streams as you need. By building your app with components that make sure they encapsulate all their dependencies.
Regards Sander -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" 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.
