You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Initially we thought that we want to support multiple templates per component, switching between them based on the the device the application is running.
But:
we never implemented this switching, as it needs to be done during compilation already
switching views is probably not enough, as different environments use different libraries, i.e. different import statements that are mutually exclusive.
We have to think about this problem more.
However, as we are currently not supporting multiple @view decorators we
should drop it.
We might add something similar later when we know exactly how this should
work...
On Thu, Mar 3, 2016 at 6:31 AM Pascal Precht notifications@github.com
wrote:
@View was dropped long time ago so closing this one. We will need to think about multiple templates per component in the future but this is whole different issue.
Activity
marclaval commentedon Mar 2, 2016
For me, there is a need to be able to build one application for various platforms or renderers.
The switch should be doable:
I fully agree that
@Viewis not enough, for example the router should be involved too.But it seemed that it would a good first step.
jpleclerc commentedon Mar 3, 2016
@Mlaval I am curious, why isn't a ngIf or ngSwitch enough to switch between templates?
0x-r4bbit commentedon Mar 3, 2016
@jpleclerc you'd still ship both templates which can be a problem on mobile.
@tbosch is there at least an alternative?
tbosch commentedon Mar 3, 2016
We have to think about this problem more.
However, as we are currently not supporting multiple @view decorators we
should drop it.
We might add something similar later when we know exactly how this should
work...
On Thu, Mar 3, 2016 at 6:31 AM Pascal Precht notifications@github.com
wrote:
lacolaco commentedon Mar 3, 2016
ViewMetadatawill be dropped too?mhevery commentedon Mar 17, 2016
#7495
ericmartinezr commentedon Mar 19, 2016
@laco0416 I think it should be removed as well, see this piece of code https://github.com/angular/angular/blob/master/modules/angular2/src/core/linker/view_resolver.ts#L97-L101 , the error message keeps referencing
@View.mhevery commentedon Mar 22, 2016
@btford can you fix the error message: https://github.com/angular/angular/blob/master/modules/angular2/src/core/linker/view_resolver.ts#L97-L101 ,
chrisnicola commentedon Mar 22, 2016
@PascalPrecht @Mlaval this seems to me like it would very solve-able at build with a tool like webpack.
pkozlowski-opensource commentedon Jun 15, 2016
@Viewwas dropped long time ago so closing this one. We will need to think about multiple templates per component in the future but this is whole different issue.angular-automatic-lock-bot commentedon Sep 8, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.