fix(angular): make sure angular form control onChange is fired when needed (#16126)

* Make sure, that angular form's onChange is not fired, when writeValue is called

* Update angular/src/directives/control-value-accessors/select-value-accessor.ts

Co-Authored-By: mmlleevvyy <levy@codeandmore.pl>

* set muteOnChange to false by default
This commit is contained in:
Mark Levy
2018-10-30 21:43:37 +01:00
committed by Manu MA
parent e9579d597f
commit d5f2e6fdd8
5 changed files with 61 additions and 5 deletions

View File

@ -24,7 +24,14 @@ export class TextValueAccessor implements ControlValueAccessor {
onChange: (value: any) => void;
onTouched: () => void;
/**
* Whether onChange should be mutted (not be fired). Will be true only when writeValue was called, which
* means that value changed inside angular form (e.g. calling setValue on a control).
*/
private muteOnChange = false;
writeValue(value: any) {
this.muteOnChange = true;
this.element.nativeElement.value = value;
requestAnimationFrame(() => {
@ -34,7 +41,11 @@ export class TextValueAccessor implements ControlValueAccessor {
@HostListener('ionChange', ['$event.target.value'])
_handleInputEvent(value: any) {
this.onChange(value);
if (!this.muteOnChange) {
this.onChange(value);
}
this.muteOnChange = false;
requestAnimationFrame(() => {
setIonicClasses(this.element);