Signal components: Why call the constructor before the required inputs and static child queries are ready? about angular HOT 4 CLOSED

Angular components are rendered in two phases: the first pass only creates elements/components, but does not process template bindings. One reason for this is that e.g. template references can capture an element forwards in the template.

The proposed input syntax does avoid the problem with strictPropertyInitialization though, as fields are always assigned using field = input.required<string>(), of which the type is string because .required was used.

from angular.

Thank you for your reply. I didn't know about such nuances with the template.

What happens if you use such a mandatory input in the constructor? Will the values ​​be ready by then? Or will an error be thrown? Will we be able to initialize other fields in the constructor using the values ​​of the required inputs?

from angular.

What happens if you use such a mandatory input in the constructor? Will the values ​​be ready by then? Or will an error be thrown?

In the current proposal it will throw.

Will we be able to initialize other fields in the constructor using the values ​​of the required inputs?

No. But you will be able to use those in a reactive context (ex. computed or a direct reference in a template).

from angular.

Understood. Overall this is a good compromise.
Thank you for your time!

from angular.