Jean-Baptiste Kaiser

Reproduced, thanks for submitting this!

Hi! Thank you for submitting this. I reproduced the issue thanks to your codesandbox. However, I noted that this issue only happens inside an `ArrayInput` component. It does not happen...

Probably linked to: https://github.com/marmelab/react-admin/issues/7591#issuecomment-1115018804

This issue still happens even after #8080. I took some time to do some testing around, and now I'm convinced this problem does not come from react-admin but rather from...

Okay so @bluebill1049 answered and it appears the format of our `errors` object is wrong in case of array fields. We should have ```ts { test: [{firstName: {....}}] } ```...

EDIT: per https://github.com/marmelab/react-admin/issues/7608#issuecomment-1513742911 it seems like I still haven't figured out 100% of the issue. Especially the following assumption I made, is wrong: > in pessimistic mode the side-effects are...

@fzaninotto I have double-checked, and indeed it appears I was wrong about this!! Hence my PR is probably targeting the wrong culprit, I need to push the analysis further... Thanks...

Now that https://github.com/marmelab/react-admin/pull/8882 has been merged I'm wondering if we can consider this issue fixed as well. Can s.o. give it a try to check if their issue is resolved...

Thanks for your analysis @smeng9 ! I have opened https://github.com/marmelab/react-admin/pull/8846 to suggest another way to fix it: when the component gets rerendered, I also check if the `container` we have...

No news for some time, closing.