[v6 rc5] form-specific change action is not bound anymore

[mihhailk]

I have quite common use-case: some fields are updating on another field change. As I have understood, in order to achieve that we should use change action creator that is injected as prop to form component.
I got it working in rc4 version, but after updating to rc5 it seems that change is not a prop anymore.
[v6 rc4] working code:

Form.propTypes = {
  change: PropTypes.func.isRequired,
  dispatch: PropTypes.func.isRequired
}

then in Form component:

updateField(field, value) {
  const {dispatch, change} = this.props;
  dispatch(change(field, value));
}

The same code in rc5 results in an warning:
Failed prop type: Required propchangewas not specified in Form

Sidenote: docs say that change should already be bound to dispatch (if I understand "actions [...] are already bound to dispatch" correctly), but it seems that in rc4 one should still dispatch it manually. Please correct me if I am wrong

[erikras]

This did change as part of the introduction of the Fields component. I will investigate. 🔍

[andrepcg]

I was too manually changing the value of some fields and it was very useful in specific situations, so this breaks my code

[erikras]

Fixed in #1588. Will post again here when it has been released. Thanks.

[erikras]

Published in v6.0.1.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.