Describe the bug
When using formik where the form name have object notation , It breaks. mapPropsToValues builds an object like {'person.name':'Person Name'} , handleChange does not seem to work fine .
I am using the Enter ${column.name}} /> where column.path has a dot within , like 'menu.name' .
I tried passing the onChange custom using handleChange with first argument as the field name and second with the value , But it did not work .
@32teeths mapPropsToValues in case of object yup type should includes within object.
mapPropsToValues = {
person: { name: 'Person Name' }
}
@sshmyg how comes yup into play here? If you want/need to separate keys which become HTML element ids you need some separator. E.g.:
{
'billingInfo.firstName':'Max',
'contactInfo.firstName':'Clementine',
}
While keeping the values object flat you are able to handle it the same way, no matter how the input/output should look like. This custom form fields are easier to implement as they don't need to handle different structures.
I hope this provides some details about the use case, at least mine.
@jaredpalmer ?
@jaredpalmer ?
@karbica How to handle nested objects are described here: https://jaredpalmer.com/formik/docs/guides/arrays
If anyone gets here while trying to do the opposite (having keys with dots instead of nesting) you should do like this:
<Field
name="['owner.username']"
label="Owner user name'"
/>
This is not documented. But I'm creating a PR. #2459
Most helpful comment
If anyone gets here while trying to do the opposite (having keys with dots instead of nesting) you should do like this:
This is not documented. But I'm creating a PR. #2459