Is ValidateOnKeepState an option?

[absolutelysimon]

We are using informed to take in fleet information for our client. They sometimes are entering 50+ instances of arrayfields, each with 50-100 fields of information to take in. The lag renders the system unusable. We are trying to using accordions to collapse each instance of an arrayField and unmount on collapse. KeepState works well for this. However, the fact that all validation is skipped makes this solution unusable, as the goal is to keep 95%+ of fields unmounted at any one time, so 95%+ of the validation gets skipped.

Is there any way to continue to validate on unmounted fields that have had "keepState" flipped on? I imagine the answer is "no" because the component and its props don't exist in that moment.

Apologies in advance for this question being recorded as an issue.

[joepuzzo]

So while informed is probably one of the most effecient form libraries out there... you are definately hitting its limits trying to render +-5,000 fields on one screen. To me this typically screams design issue. No human can possible look at all those fields at once. Typically in these cases I first go back and re evaluate the design of the page ( maybe it needs pagination or something )

That being said, if you for some reason really need that many fields on one screen... WHICH AGAIN I WOULD HIGHLY ADVISE AGAINST... then you can use form level validation instead

In other words pass a validate function to the form component and perform validation there.

[absolutelysimon]

Ya, accordions make more logical sense for our use case than pagination. Honestly we plugged AI into the intake portion of our system and now our clients are pushing through much bigger chunks of data than we expected, so this is our rework.

We're triggering validation on dismount now using your suggestion and saving the error state separately. Should be working well shortly. I doubt anyone else would want validation connected to the keepState props.

Thanks for the great library and the comment, and all the work you put into this before you were paid for it. We've been using it happily for almost a decade.

I'll leave it to you to close the issue, I don't have any concrete suggestions.