Surrounding index.html tags within app component my be nice to have.

I Think the angular 2 approach is get data from APIs and render all things from client. But with MVC server frame work we have many features to have. With the angular2 approach I think we must release that features and just send data to the client.

In some case we just need some ajax call to server to do some functionalities (e.g like a thing , add it to favorites,…) We can do this cases with angular 1 but with angular2 can’t and we must to create corresponding components for MVC server side views and it is re architecture any things again. In my opinion surrounding index.html tags with app component my be nice to have.

<app>
existing html tags
</app>

thanks for attentions.

[DzmitryShylovich]

@zoechi it’s not actually true. See https://github.com/angular/angular/issues/4946#issuecomment-275853207

[abram27]

Is there a reference on how this would be a issue with security? Seems no different than manually injecting a different templateUrl into a component. Nevermind, decided to drop angular 2 from our projects, it seemingly is missing a lot of features for integration with other frameworks. The division of packages seems odd since you can’t use the features in isolation. Guess it probably works well in a silo if you are willing to take on the whole framework and specifically for a spa.