We are developing a corporate component library which should provide Material Designed Angular Components. So the users of this library are not supposed to use e.g. Angular Material directly but rather include some component like "custom-tabs".
Using the components of MatTabModule directly works like a charm, whereas when using our custom components the projected content does not show up.
Usage looks very similar to the Angular Material API:
<custom-tabs>
<custom-tab [label]="labelA">Content A</custom-tab>
<custom-tab [label]="labelB">Content B</custom-tab>
<custom-tab [label]="labelC">Content C</custom-tab>
</custom-tabs>
The custom components try to project the content as follows:
<!-- custom-tabs template -->
<mat-tab-group>
<ng-content></ng-content>
</mat-tab-group>
<!-- custom-tab template -->
<mat-tab [label]="label">
<ng-content></ng-content>
</mat-tab>
Does anyone have an idea how we can get it working?
I provided a StackBlitz where you can see the problem in action.
I think the issue you have is the same described in this github issue: https://github.com/primefaces/primeng/issues/1215
Basically the problem here is that ng-content does not provide @ContentChild when crossing component boundaries.
You can see that mat-tab uses @ContentChild: https://github.com/angular/components/blob/master/src/material/tabs/tab.ts#L56
So I think the only solution is to override it programmatically the way it is described in primeng issue.