Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

onChange doesn't provide mapped model #478

Open
amannn opened this issue Sep 19, 2017 · 0 comments
Open

onChange doesn't provide mapped model #478

amannn opened this issue Sep 19, 2017 · 0 comments

Comments

@amannn
Copy link

amannn commented Sep 19, 2017

It looks like the data that is passed as the first argument to onChange is from getCurrentValues which doesn't call mapModel, therefore dots within field names aren't resolved to nested objects.

However onSubmit is passed the mapped model.

Is there a reason for this behaviour? From my perspective it would be correct to also map the model that is passed to onChange. It looks like there was some discussion about this in #224, but this never made it to the code base.

Would you be open to a PR implementing the proposed change? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant