{"action":"created","issue":{"url":"https://api.github.com/repos/angular/angular/issues/7596","repository_url":"https://api.github.com/repos/angular/angular","labels_url":"https://api.github.com/repos/angular/angular/issues/7596/labels{/name}","comments_url":"https://api.github.com/repos/angular/angular/issues/7596/comments","events_url":"https://api.github.com/repos/angular/angular/issues/7596/events","html_url":"https://github.com/angular/angular/issues/7596","id":140693975,"number":7596,"title":"Final statement about ngInclude alternative","user":{"login":"PavelPZ","id":2981508,"avatar_url":"https://avatars.githubusercontent.com/u/2981508?v=3","gravatar_id":"","url":"https://api.github.com/users/PavelPZ","html_url":"https://github.com/PavelPZ","followers_url":"https://api.github.com/users/PavelPZ/followers","following_url":"https://api.github.com/users/PavelPZ/following{/other_user}","gists_url":"https://api.github.com/users/PavelPZ/gists{/gist_id}","starred_url":"https://api.github.com/users/PavelPZ/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/PavelPZ/subscriptions","organizations_url":"https://api.github.com/users/PavelPZ/orgs","repos_url":"https://api.github.com/users/PavelPZ/repos","events_url":"https://api.github.com/users/PavelPZ/events{/privacy}","received_events_url":"https://api.github.com/users/PavelPZ/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":20,"created_at":"2016-03-14T14:43:56Z","updated_at":"2016-04-02T17:57:08Z","closed_at":null,"body":"I am very sorry for making dupl of #2753. But after closing this issue on 2 Jul 2015, there are a lot of compelling arguments from community for allowing this feature.\r\n\r\nI read [this article](http://stackoverflow.com/questions/34421869/templatecache-in-angular-2) with statement: *It is no longer possible to implement ng-include...*.  \r\nI only want to make sure that: \r\n- angular team is really not interested in supporting any \"html template as data or as parameter\" scenario (for incoming angular2 release candidate)\r\n- there cannot be provided any official workaround, avoiding to have single angular2 component for every product in catalogue, for every web page, for every eLearning exercise etc.? \r\n\r\n\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/angular/angular/issues/comments/204765755","html_url":"https://github.com/angular/angular/issues/7596#issuecomment-204765755","issue_url":"https://api.github.com/repos/angular/angular/issues/7596","id":204765755,"user":{"login":"wardbell","id":129061,"avatar_url":"https://avatars.githubusercontent.com/u/129061?v=3","gravatar_id":"","url":"https://api.github.com/users/wardbell","html_url":"https://github.com/wardbell","followers_url":"https://api.github.com/users/wardbell/followers","following_url":"https://api.github.com/users/wardbell/following{/other_user}","gists_url":"https://api.github.com/users/wardbell/gists{/gist_id}","starred_url":"https://api.github.com/users/wardbell/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wardbell/subscriptions","organizations_url":"https://api.github.com/users/wardbell/orgs","repos_url":"https://api.github.com/users/wardbell/repos","events_url":"https://api.github.com/users/wardbell/events{/privacy}","received_events_url":"https://api.github.com/users/wardbell/received_events","type":"User","site_admin":false},"created_at":"2016-04-02T17:57:08Z","updated_at":"2016-04-02T17:57:08Z","body":"I'd like to document. But I don't think i understand the scenarios well enough.\r\n\r\nMany ways to skin this cat. When the variations are few, IMO, its not a big deal to write a component per variation and use ngSwitch. In my A1 life I only used ngInclude for small variation sets and so I don't miss it in A2\r\n\r\nThe volume requirements from @tolemac beg for a different kind of approach such as the entity metadata driven ideas in the \"Dynamic Forms Cookbook\" (see the docs).\r\n\r\nBut that may be _too_ general. I sense that @tolemac would like to write custom screens for each of the 400 entities.\r\n\r\nThat need not imply 800 files; with such small html, inline templates should be fine, at least most of the time.\r\n\r\nI think the inheritance/mixin issues can be addressed adequately. It will take some more thought and help from this group.\r\n\r\nI'm noodling it! "}}