-
-
Notifications
You must be signed in to change notification settings - Fork 70
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
Bug - deleting row #145
Comments
I stumbled upon the same problem. Have you found a solution @omerman ? |
@OnkelTem Instead of relying on the dirty fields for arrays with delete option.. I checked versus the initial values instead.. |
It's really irritating :( |
It is, but to fix it you'd have to have some breaking changes.. like enforce a unique Id for each row. It is possible.. but seems like a lot of work.. |
Assuming we render the array with editable items,
like so,
{fields.map((arrPrefix) => <Field name={
${arrPrefix}.val1} />}
When deleting a row of a field array
all of the indexes following the row becomes dirty, in the
form.dirtyFields
.I think it happens because the Field component of say item[1].val1
isEqual
will return false once deleting say item[0].val1.I think the isEqual should be different when the
Field
is looking at a nested array field, surely a change inField
would be wrong, but Im thinking there should at least be aFieldArrayCell
that will render also accept id prop(along withField
props) and will use this to send theisEqual
the correct values, and then, the isEqual will evaluate correctly, andform.dirtyFields
will be correct.The text was updated successfully, but these errors were encountered: