Benjamin Millagou

Hi there, I did not real all of the above, so sorry if the question has already been asked or is completely dumb. Can't namespaces be inferred from the name...

I tried to keep track of keys on my side but I encountered another problem Calling `fields.remove(index)` trigger 2 renders, a first where the deleted field is still present, a...

It seems that queuing keys handling in a microtask allow the key handling to take place between the "bad" and the "good" render Also, exposing an unique id here could...

https://codesandbox.io/s/react-final-form-field-arrays-mrl4s works cause I queued key handling in a microtask, which is not something I want to do https://codesandbox.io/s/kx8qv67nk5 looks like its working, but the issue is present, it's just...

I think I'm on the wrong path, the id should somewhere in the `final-form-arrays` or `react-final-form-arrays` lib

> Could you explain how https://codesandbox.io/s/kx8qv67nk5 is broken? > (or rather, how to reproduce the bug you are describing) https://codesandbox.io/s/react-final-form-field-arrays-tc2tk Open the codesandbox console, add 2 customer with different values,...

> Also, isn't this related? > #114 Does not look like it

The best workaround so far seems to handle keys manually in microtasks as seen in https://codesandbox.io/s/react-final-form-field-arrays-mrl4s I also updated the exemple to better show the issue : - open the...

> Calling fields.remove(index) trigger 2 renders, a first where the deleted field is still present, a second with the field correctly deleted. @erikras Any idea why there is an incorrect...

After investigation of those 2 renders, there seems to be a bug of synchronization of field states https://codesandbox.io/s/react-final-form-field-arrays-3t4ol step to reproduce : - open the codesandbox console - create a...