Behavior difference between form.validate() and basic client-side validation

[WataruNishimura]

I encountered a difference between form.validate() and basic client-side form validation with Material UI and valibot plugin.
I believe this is intentional, but this behavior does not seem to be mentioned anywhere in the official Conform documentation.

form.validate() behavior

• validate every value
• reflect every value's error whether if its field is dirty or not

basic validation

• validate every value
• reflect value's error only its field is dirty

repro

https://stackblitz.com/edit/conform-validation-difference-repro?file=pages%2Fform.tsx

If it's truly intentional, could I update validation section in two language?

Thank you for your contributions to this great form library.

[edmundhung]

Hi @WataruNishimura,

The validate intent supports both form and field level validation. When you call form.validate(), it marks every field in the form touched. So any errors in the result will be shown directly. This is similar to clicking on an submit button, except that no submission will be made. If you call form.validate(name) instead, it marks only that field as touched, and only touched fields with errors would be shown. This is also what Conform uses internally when you have shouldValidate or shouldRevalidate configured.

[WataruNishimura]

Thank you for your reply.

I undestand form.validate behaviors both form and field level.
Can I append that api specification both form and field level validation to validation section?

[edmundhung]

Yes, that would be really helpful. Thank you!