Update mock component to allow setting values on a parent reactive form via the component

Hi, Nice Library!

Would you be open to updating your mock component to allow Reactive Form values to be propagated out. I like to drive the reactive form, via the form element component, when I am testing so that I know that it is bound correctly.

Something like this:

Sample Class

export class MockReactiveFormsElement implements ControlValueAccessor {
  propagateChange = (_: any) => {};
  setTouched = (_: any) => {};

  writeValue(value: any) { }

  registerOnChange(fn) {
    this.propagateChange = fn;
  }

  registerOnTouched(fn) {
    this.setTouched = fn;
  }

  setDisabledState(isDisabled: boolean) {}
}

Use in your test like this:

const typeSelect: MockMdSelectComponent = fixture.debugElement.query(By.css('md-select')).componentInstance;
typeSelect.propagateChange('Ninja');
expect(component.warriorForm.value.type).toEqual('Ninja');

Maybe use __propagatesChange or some type prefix so as not to clash with a component that has that method, or it could be a subclass that has a seperate function mockReactiveFormComponent

Happy to submit a pull request if you will merge. Just let me know your preferred approach.

[ike18t]

fe547af8d357a477774a161c0dcda7dd417ca7bb

[vespertilian]

Yeah I had a great weekend, I was actually at a JavaScript camp. https://ix.campjs.com. So I figured it would be a good place to get the work done but every-time I tried to go to Github the 100+ other devs were also trying to download something, so I just gave up on the third timeout attempt.

I could have tried harder, but there were also waterfall walks and mountain vistas to checkout.

https://twitter.com/campjs