@mhevery opening a PR to kick off detailed discussion on the NgInsert / NgOutlet directive discussed in #7615.

Opening a PR with the simplest possible and useful implementation. We can gradually add more features like:

• passing local variables
• ability to insert components, not only TemplateRef

cc @jelbourn

@pkozlowski-opensource Thanks for kicking this off!

I think it's important to consider component loading in the initial API; in particular, we may want a single property that can be set to load either a TemplateRef or a component (rather than always taking TemplateRef). I like the idea of some wrapper object (like how we have Portal) because it lets you add additional information/metadata to whatever you're loading (such as locals for a TempateRef or an origin ElementRef for a component).

Looks, good. Sorry, my only comment is about name (bit o bikeshedding.)

@mhevery thnx for the review. I like the suggestion of having <template [ngInsert]="exp"> syntax as indeed, it will avoid those "dangling" elements. Will change / update the PR. (my part of bikeshedding here: it still bothers me that we use <template> both as a capture and insertion points, but not sure why... Why I would like to see them as distinct concepts? I can't think of good reasons, but yeh,....)

@jelbourn yep, let's build on top of this for components, locals etc. I will be in MTV in 4 weeks so we can iterate on this one.

@pkozlowski-opensource what is your thought on ngOutlet istead of ngInsert?

I am with you on using template for both input and output. But like you other than aesthetics not sure why it matters. Keep in mind that template is part of the web spec, so if we do come up with template-output we would be breaking away from the spec.

we could do comments <!--nd-directive: [ngOulter]="expression" -->

what is your thought on ngOutlet istead of ngInsert?

I've "tested" ngOutlet on people in my office and it was too confusing with a router - this is why I've proposed NgInsert in this PR.

I think <template> is just fine for both. Adding behavior to comments strikes me as extremely unexpected behavior.

I also like ngOutlet over ngInsert. If you're just doing to support TemplateRef, though, a more meaningful name would be TemplateHost.

OK, did all the renamings / refactors discussed in the PR. Rebased, build is green.

The PR looks great, but we got into a naming discussion. The issue is that insert implies that you are adding an item to a list, in this case the TemplateRef. But in our case what is being inserted is a View not a TemplateRef, it is just that we get the View from the TemplateRef, so we don't think we want `insert.

Sorry, I know this is bikeshedding, but naming is important.

The team thinks we should call it ngTemplateOutlet to be aligned with routeOutlet since they do a very similar things, one with TemplateRef the other with Route

Personally I don't feel too strong about names so I'm perfectly fine with ngTemplateOutlet. Will update the PR accordingly.

Thnx for looking into this / discussing!

@mhevery did the discussed renaming. Dart build is failing but I don't think it is related to my change.

Yes, dart change is unrelated.

Merging PR #8021 on behalf of @robertmesserle to branch presubmit-robertmesserle-pr-8021.

Hello, Im trying to use this feature but with no success.
I tried following this example: http://5thingsangular.github.io/2016/04/18/issue-2.html
but with no succuess, no matter what I do I get an template parse error. I wrote the entire problem with more explanation on stack overflow as well:
[http://stackoverflow.com/questions/36965977/ngtemplateoutlet-doesnt-work-for-me](NgTemplateOutlet doesn't work for me)

I will really appreciate any help with this

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.}