Erik Rasmussen

Hey man. Finally getting back to this. I think I may have stopped watching your talk after I'd concluded that you had a good point, but before you called out...

Okay, all the issues you've linked to have been fixed/resolved. However, I don't think I can merge this PR, because it's still breaking for reasons that I think are problems...

Hmm.. I hated adding that `setTimeout` in #4, but I didn't see any other way around the problem in final-form/final-form#26. Perhaps it will have to be revisited and thought about...

Yes, `parse`/`format` is functionality from RFF that wasn't implemented here. I'll think about how best to add it. The field-level validation could be added easily via the "field config" prop...

I didn't mean for you to close this. It's still a legit feature request.

Great insight. 👍 The dev stuff can be hard, as we currently have no test suite. I've had some success in the past consuming a library as I write it...

No. This is _not_ resolved. In fact, my `[email protected]` fix mistakenly assumed that that sort of movement was the only problem, but `unshift` is a different beast. ⚠️ Still in...

Can you show me a sandbox it worked on, with older versions, and a sandbox it doesn't work on with newer versions?

@davidhenley I'm confused. On Dec 14, [you agreed that it was fixed by `v1.3.5`](https://github.com/final-form/react-final-form-arrays/issues/3#issuecomment-351742188), and then on Dec 21, [you post a failing sandbox that is using `v1.0.0`](https://github.com/final-form/react-final-form-arrays/issues/11#issuecomment-353471281).

Great!