Shouldn't form.setFieldValue trigger the field validation by default?

[rodrigofariow]

I'm trying to update a fieldA value programmatically from anywhere else besides it's own <form.Field name="fieldA" /> usage, I have found 2 ways to force validation to run:

form.fieldInfo.fieldA.instance?.handleChange('1')

form.setFieldValue('fieldA', '1')
form.validateField('fieldA', 'change')

I would expect validation to run when using setFieldValue since it does update meta data too. But it does not.
Is this intentional?

NOTE:
My use case is NOT a linked field.

Cheers

[harry-whorlow]

@rodrigofariow bare with me as I'm fairly new, but I'm going to say this is intentional... form.setFieldValue is used globally thought the library for setting values, you'll find it in formApi multiple times and fieldApi also a couple. So there's situations where we don't want to re-validate the field when we call it by default.

However if you take a peek into the source code, you'll see that for the setValue for Field we're actually doing exactly what you are:

Where this.validate('change') is just validateField that has been pre-populated. So what you've done is not wrong, though I could ask the other maintainers if theres interest in adding an additional opts for validating on the form.setFieldValue?