Question: Dynamic template/ controller

[dbabaioff]

In our app we have some routes that based on a condition need to load a different template/ controller.
For example, the homepage route (/) if the user it's logged in we need template A.html / controller A and if not we need B.html / controller B.

Will such a use-case be supported by the new router?

[btford]

If I understand, more generally:

• You want to be able to route based not just on parameters, but also on some state elsewhere.
• You want to be able to route without changing the URL or pushing a state to the router's history.
• You want to be able to use both behaviors at the same time.

I want to support the first item. I'm not sure I think the router should support the second or third items. For your case, I'm not sure this really should be the job of the router. Why not:

<div>
  <login-component ng-if="!user.isLoggedIn"><login-component>
  <logged-in-component ng-if="user.isLoggedIn"><logged-in-component>
</div>

[tinusn]

@btford The first item is a feature of the ui-router project (template and controller Provider - see https://github.com/angular-ui/ui-router/wiki#templates) and would be nice to have in this new router.