How is one meant to perform a silent validate? (v4)

[Winston-Guess]

It seems there is no way to perform a silent validate(). Do I need to perform a resetForm() after validating? Does that not revert all field values to their original state?

It would be great if their were a silent option for vaidate() and/or if there was a resetFormErrors() function available.

[logaretm]

At the moment there isn't without calling resetForm which would indeed reset everything.

This might be worth adding.

For the meantime, you could use resetForm and have it reset the values to the current values:

const { values, validate, resetForm, meta } = useForm();

async function validateSilent() {
  const result = await validate();
  resetForm({ values, touched: meta.value.touched });
}

May I ask why do you need silent validation? what is your use-case.

[Winston-Guess]

I found the silent validation very useful in v3. I've got a mobile webpage builder that has validation on each of the different kinds of builder elements (e.g. text, image, button). When the user switches to another element I validate the current element and update the tally of incomplete/invalid elements. I have a button that shows the number of incomplete elements that acts a notification to the user that his webpage is incomplete/invalid and allows them to cycle through these elements.

If the user then navigates to an incomplete element and updates a field so that it becomes valid, I want this to adjust the count of invalid elements as soon as the current element/form becomes valid. But I do not want to trigger a validation when form settings change because I have an animation that is linked to invalid form check, which I do not want triggered each time a value is changed and the form is found to be invalid. This acts like the eager mode in v3 but on the form as a whole.

You'll probably recall that I have another discussion on interaction modes not being applied in v4 and this seems to somehow mimic that. Apparently I'm a fan of being eager -_-;; I'll use your solution in the meanwhile but I do think a resetFormErrors function would be valuable.