Matthieu Riegler

@e-oz Reading a required input will always fail in the constructor. Your example exhibit an expected behavior.

v19 introduced timing changes for `effect`. `effect` runs before a component in checked the a CD cycle. Which explains why the queries are undefined. If you want an effect that...

I've have some explainations about the changes in v19 in this article: https://riegler.fr/blog/2024-10-15-effect-context/ `afterRenderEffect` is the effect that runs after CD. > afterRenderEffect [...] is typically used to replace `ngAfterViewInit`....

`afterRenderEffect()` is not only for DOM manipulations but for any case where an effect needs to run after rendering. Having children is exactly that.

This is more or less the discussion we're having in this issue. This is indeed confusing.

The way angular's synchronization works, you don't even need such an extension. You can use the "paint flashing" feature of the devtools.  Every flash you'll see we'll be due...

Removing the labels, this is actually a guide we'll will rewrite soon.

#62250 will address this.

Hi Can you please provide a working repro (that plunkr doesn't work), with stackblitz for example and with an up-to-date version of angular.

This is actually a duplicate of #34252.