Erik Rasmussen

Results 92 comments of Erik Rasmussen

[Twitter thread about the "thousand field problem"](https://twitter.com/erikras/status/1129048162797277184). @alirezavalizade, I don't know how easy it would be to throw your thing in there, but if it's doable, I'd love to have...

BTW, to the original poster, @romeovs, RFFv5 (and now v6) made a significant change, allowed by the glory of hooks, to how field-level validation is done on first render. This...

Can you show me a render counting test that passes if `meta` and `input` are memoized but fails if they are not?

The reasoning for this decision is somewhat explained [here](https://github.com/final-form/final-form/blob/master/docs/faq.md#why-does--final-form-set-my--field-value-to-undefined). Your `notRemoveWhenEmpty` proposal sounds like a decent compromise. πŸ‘

This test is not `expect`ing anything. I don't really understand the problem. Can you make it fail?

What am I supposed to see when I load up your codesandbox? Clicking the button makes the other fields appear. I'm not seeing any errors.

It might be nice to give `FormApi` a `serialize`/`deserialize` api.

Life circumstances mean that I no longer have the time to _actively_ maintain this package. But yes, I'd be open to having someone help maintain the package. DM me on...

You'll probably have to maintain a data structure of which fields are on which pages, so you can grab `Object.keys(errors)[0]` and figure out what page that field is on.

I'm afraid that any library that is going to manage 1,500 controlled inputs is going to run into performance issues, _especially_ if you are going from 0 to 1,500 fields...