contentChild support locator array about angular HOT 2 OPEN

It is an interesting request and one that would be relatively easy to support but as always, before extending the API surface, would love to hear about real-life use cases.

In my thinking content queries establish API contract between a component and its content. In a sense content queries are like inputs. From this perspective it is not immediately clear to me why this contract would be so loosely expressed that it would allow both explicitly named things (string) and types. This is why I would be very interested in the scenario where it is helpful.

from angular.

It is an interesting request and one that would be relatively easy to support but as always, before extending the API surface, would love to hear about real-life use cases.

In my thinking content queries establish API contract between a component and its content. In a sense content queries are like inputs. From this perspective it is not immediately clear to me why this contract would be so loosely expressed that it would allow both explicitly named things (string) and types. This is why I would be very interested in the scenario where it is helpful.

I have developed a library for using React in Angular. One of the operations is to project any element/component/templateRef onto React children, but before projection, it needs to be processed and manually added to React, so any projected element needs to be queried

from angular.