Add the descendants option to ContentChild

🚀 feature request

Relevant Package

@angular/core

Description

Similar but opposite to how the ContentChildren decorator has descendants option to query all descendants, I would like ContentChild to have an option to query only direct descendants.

Describe the solution you'd like

Add descendants as a metadata property for ContentChild
If descendants is true or undefined, query all descendants (preserves current behavior)
If descendants is false, query only direct descendants

The expected behavior, for example, would be that a component (my-component) which may or may not expect a content child directive (my-directive) will not catch said content child directive from the nested component.

I can make a working example if this pseudo-example doesn't explain very well

<my-component>
    <my-component>
        <ng-template my-directive></ng-template>
    </my-component>

    <ng-template my-directive></ng-template>
</my-component>

VS

<my-component>
    <my-component>
        <ng-template my-directive></ng-template>
    </my-component>
</my-component>

Yep, we should definitively add the descendants option for ContentChild, was bitten by the lack of it several times already!

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.

It would be nice if the bot posted a link to the poll itself. I had no idea where to vote.

I don't see any links in the documentation.

Is the voting just done on this issue?

Yes, it's done using reactions on the issue.

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.

Is this not considered? If someone has optional templates with nested components the parent can pick children templates and consider them like its own, which is wrong

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

Navigation Menu

Repository navigation

Add the descendants option to ContentChild #31921

🚀 feature request

Relevant Package

Description

Describe the solution you'd like

1 remaining item

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Add the descendants option to ContentChild #31921

Description

🚀 feature request

Relevant Package

Description

Describe the solution you'd like

Activity

the-avid-engineer commented on Jul 30, 2019

pkozlowski-opensource commented on Sep 17, 2019

angular-robot commented on Jun 4, 2021

angular-robot commented on Jun 24, 2021

the-avid-engineer commented on Jun 24, 2021

1 remaining item

the-avid-engineer commented on Jun 24, 2021

the-avid-engineer commented on Jun 24, 2021

Airblader commented on Jun 24, 2021

angular-robot commented on Jul 24, 2021

Xriuk commented on May 26, 2022

angular-automatic-lock-bot commented on Aug 1, 2022

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions