You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
because of this , it makes me hard to write reusable component which take advantage of ControlValueAccessor. As we know that this interface has 2 important methods, one is writeValue and the other is ngChange. Imagine, I have a local form group in my reuseable component, every time I update this form control in writeValue method, it triggers ngModelChange of every control of this form group. In valueChanges method, for every change, it triggers ngChange which updates formControl. Hence, it makes circular update from writeValue to ngChange and otherwise.
Can ant team implement change event rather than ngModelChange?
What does the proposed API look like?
ngModelChange
The text was updated successfully, but these errors were encountered:
What problem does this feature solve?
because of this , it makes me hard to write reusable component which take advantage of ControlValueAccessor. As we know that this interface has 2 important methods, one is writeValue and the other is ngChange. Imagine, I have a local form group in my reuseable component, every time I update this form control in writeValue method, it triggers ngModelChange of every control of this form group. In valueChanges method, for every change, it triggers ngChange which updates formControl. Hence, it makes circular update from writeValue to ngChange and otherwise.
Can ant team implement change event rather than ngModelChange?
What does the proposed API look like?
ngModelChange
The text was updated successfully, but these errors were encountered: