A practical guide to Angular Template-Driven Forms about timdeschryver.dev HOT 4 CLOSED

@timdeschryver Thanks for the answer. I saw that people suggest using setTimeout. For me, it is the last resort; however, it can be useful in many cases. If you know what you do and don't add it everywhere.
My first team lead liked to joke that setTimeout = 0 resolves 90% issues and setTimeout = 100 - 99%. 😆

from timdeschryver.dev.

Thanks for such informative article.

I've one problem with tempalte-driven forms. We have a very big form with dynamic fields. So, tempalte-driven forms looks very useful here, since we don't need to add/remove validations manually. Because we've many toggles which can show or hide fields.

The whole form was split by sections. And I need to show some markers near each section when it's valid or not. However, it's very hard to get access to nested form controls. I've tried to get acees to NgModelGroup inside each section, but on ngAfterViewInit form control is not available.

Maybe you had such situations and could help with that? Currently I see a few solutions - use reactive forms, but it would require manually clear validations and fields. Or try to put the whole form into one component, but I'm not sure that it's really change anything.

from timdeschryver.dev.

Regarding my previous question. I found one more workaround. Subscribe on form valueChanges and as soon we get needed field there, we can get control by name and switch stream to its statusChange.

from timdeschryver.dev.

Hey @NechiK , yes I do find this one of the quirks.
In those cases, I usually subscribe on form value changes (as you mentioned).
Or you can also set a setTimeout in the AfterOnInit, that way the formgroup exists.

from timdeschryver.dev.