Implement Missing Features for View

NOTE: Please add use cases for anything not yet covered here that should be considered.

Features currently missing from @View:

• More than one @View for a component
• Move CSS from <style>@import()</style> into @View annotation.
  • Needed for inlining during build step
  • Often times same HTML may have different CSS for styling
• Selectors:
  • CSS (as in <button> vs <button ios-style>)
  • platform as in iOS, android, desktop
  • screen size

[sallampalli]

I am surprised to see this as a missing feature. This was so easy to do in Angular 1.x.x. in directives, There will be lot many use cases which drive conditional templates/multiple Views. I might need the same component, its data, config etc. but a slightly different view . Something like this would have been great

/*Just making this up as an example */
@Component({
selector: 'sample-selector',
properties: ['mode'], 
template:function(){
if(this.mode==='simple'){return '<h1 ngFor="....">{{.....}}</h1>';}
else{return '<button ngFor="...">{{...}}<button>'}
}
});

Is there another way to deal to achieve this ?

[nicksloan]

@mhevery It’s pretty unhelpful to close an issue as “obsolete, and longer relevant / actionable” with no explanation at all. Can you provide some context?