Dependent Field Validation Error Not Automatically Cleared

[sriyabro]

Issue: Dependent Validation Error Not Automatically Cleared

Description

When using cross-field validation with validate function, errors in a dependent field are not automatically cleared when the referenced field is modified.

Steps to Reproduce

1. Create a form with two number inputs: minValue and maxValue
2. Add a cross-field validation that checks maxValue against minValue
3. Enter a scenario where the initial validation fails (e.g., minValue = 100, maxValue = 50)
4. Modify the minValue to a value that would make the original validation pass (e.g., minValue = 10)
5. Observe that the maxValue field still shows the previous error

Minimal Reproducible Example

const Form: React.FC = () => {
  const {
    register,
    handleSubmit,
    formState: { errors },
  } = useForm<FormValues>({
    reValidateMode: 'onChange',
    criteriaMode: 'all',
  });

  const onSubmit: SubmitHandler<FormValues> = (data) => {
    console.log('Submitted data: ', data);
  };

  return (
    <div>
      <input
        {...register('minValue', { required: true })}
        type="number"
      />
      <input
        {...register('maxValue', {
          required: true,
          validate: (value, { minValue }) => {
            // Error persists even after minValue changes
            if (value < minValue) {
              return 'maxValue should be greater than minValue';
            }
            return true;
          }
        })}
        type="number"
      />
    </div>
  );
};

Expected Behavior

When the referenced field (minValue) changes and would resolve the previous validation error, the dependent field's (maxValue) error should be automatically cleared.

Actual Behavior

The error in the dependent field remains even after the referenced field is modified to a value that would pass the validation.

Proposed Solution

Implement a mechanism to automatically re-validate and clear errors in dependent fields when their referenced fields change.

Reproduction Link

StackBlitz Demonstration

Additional Context

This issue impacts form usability, as users must manually edit the field with the persisting error even after resolving the underlying validation condition.

[sriyabro]

Resolved
Refer to the comment on Issue 12831