-
Notifications
You must be signed in to change notification settings - Fork 26.5k
Description
I'm submitting a ... (check one with "x")
- bug report => search github for a similar issue or PR before submitting
- feature request
- support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
Current behavior
Doesn't seem possible to do it in an easy way without not use framework core stuff
Expected behavior
To be able to determine by an asynchronous condition (a condition that will be resolved later) which component to load in a route.
What is the motivation / use case for changing the behavior?
I'd say the following is a very common behavior expected on any medium size app:
Let's say you have a dashboard (just after you login). You wanna keep 2 different components UserDashboard and AdminDashboard (for not filling your template code with *ngIf), but that condition cannot be resolved immediately because the role comes from an API, so then you cannot "right away" conditionally pass one component or another to a specific route.
This doesn't seem to have an answer that implies not to compile and load a component by yourself.
Please, check out http://stackoverflow.com/questions/39688929/angular-2-how-to-conditionally-load-a-component-in-a-route-asynchronously
- Angular version: 2.0.1