ng-content select does not work when content is in a *ng-for loop

[typotter]

When providing an element selector to the ng-content tag, the contents are not transcluded.
Example:

my-component template

<div>My Items</div>
<ng-content select="my-item"></ng-content>

caller template

<my-component>
  <my-item *ng-for="#item of items">{{item}}</my-item>
<my-component>

In this example, the my-item components are not transcluded. If they are not in a for loop, then they are picked up. example:

<my-component>
  <my-item>Item 1</my-item>
  <my-item>Item 2</my-item>
<my-component>

[matanlurey]

I think this is WAI, @tbosch would know best.

[tbosch]

yes, this does not work right now. However, what does work is this:

<my-component>
  <template ng-for #item [of]="items" class="item"><my-item>{{item}}</my-item></template>
</my-component>

...
<ng-content select=".item">

I.e. we are checking the template element to be projected, as <my-item *ng-for> actually is just a shorthand for the above code. However, we probably want to support this case as well...

[kara]

@tbosch The syntax in your example is now [ng-for-of] rather than [of], right?

  <template ng-for #item [ng-for-of]="items" class="item">

Here's a plunker of the working code for anyone else playing around with this:
http://plnkr.co/edit/Hn393B9fJN6zgfaz54tn

[tbosch]

@kara yes, this is correct.

[woppa684]

Any update on when this will be fixed?

[tbosch]

This should work as of aa966f5

[uMaxmaxmaximus]

in my framework is works ^^ https://www.youtube.com/watch?v=tmKMAfzR8Ow

[angular-automatic-lock-bot]

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