Never again be confused when implementing ControlValueAccessor in Angular forms

[maxkoretskyi]

Dive deep into the implementation details of the ControlValueAccessor that acts as a generic mechanism between Angular’s formControl and a native/custom form control and learn how it works and how to use it correctly.

Read the article here.

[alexandis]

I have two mutually dependent controls (dropdown and textbox). Changing one makes change to another (via setValue). However, I can't get rid of auto-triggering back the initiator's valueChange...

[adaico]

The best choice is not to use dropdown as ValueAccessor, because I believe that you can't use it in forms independently from other components.
If we have a fact, that dropdown is ValueAccessor, you should use { emitEvent: false } flag when you set control value to dropdown and not to emit event from dropdown in writeValue hook.