Maxim, you did a great and useful job of explaining this issue. I clicked the heart. However, you did recommend against using setTimout to affect the timing. I lost a lot of hours researching after reading this and then I found that the Angular docs use it. It is a hack as everyone feels but this seems to be the official work around. Maybe reword this:
“If you google around you will probably find two most common fixes for this error — asynchronous property update and forcing additional change detection cycle. Although I show them here and explain why they work I don’t recommend using them but rather redesign your application. I explain why in the last chapter.”
I found your explanation in the last chapter to be too vague to be useful. Basically just re-architect the components. So I showed you the code in my child form. As far as I understand there is nothing to re-architect and still have a form that gets imported into other components such as add a member and edit a member. DRY. More specific guidance on what you mean by re-architect with some examples would be hugely helpful.
Again, thank you very much for your explanation!!!
Jim