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
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.
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!
The text was updated successfully, but these errors were encountered:
It looks like the data that is passed as the first argument to
onChange
is fromgetCurrentValues
which doesn't callmapModel
, 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!
The text was updated successfully, but these errors were encountered: