Support for setting Input Signals programmatically for projected content children

[Fernker]

Support for setting Input Signals programmatically for projected content children

[Harpush]

@Harpush is the setInput available automatically when using @ContentChildren? I've only used it with dynamic components and still am not clear if it's currently available?

No it isn't. The issue I linked suggest adding it to injection of host component from directive. This issue seems half way similar as it can be solved if content child could get not the component instance but the component ref instead.

[alxhub]

@RobbyRabbitman just note that SIGNAL isn't public API.

[Harpush]

One can say it is half way related to #47398
As injecting the component ref of the projected component (in this case with content child) would allow setInput usage

[Fernker]

@Harpush is the setInput available automatically when using @ContentChildren? I've only used it with dynamic components and still am not clear if it's currently available?

[Fernker]

Although setInput seems pretty broadly typed, which might make sense with a ComponentRef but it would need to be narrower to be most useful.

[Harpush]

Although setInput seems pretty broadly typed, which might make sense with a ComponentRef but it would need to be narrower to be most useful.

There is an open issue for better setInput types too

[Fernker]

Would the componentRef still include a reference to the component class to be able to access other methods on the class that aren't inputs?

[RobbyRabbitman]

I had a similar situation, which was solved by unwrapping the Signal Input with the SIGNAL symbol and use setSignalValueFn (or something like that... typing this comment from mobile). I don't know if that's intended, but it worked :D