VeeValidate v4 and Yup/Zod schema replacement: re-validation and stale errors

Direct Answers

Yes, changing validationSchema triggers automatic re-validation of current form values against the new schema in VeeValidate v4.

Yes, errors for fields that exist in the old schema but are omitted from the new schema are cleared automatically during this re-validation pass.

Yes, the behavior is consistent between Yup and Zod integrations because both route through VeeValidate's normalizeSchema adapter, which returns a standardized validation function.

How It Works

VeeValidate's useForm composable watches the validationSchema option. When the reference changes (detected via Vue reactivity), it schedules a re-validation on the next tick using the current form values. The watcher respects your configured validation triggers (onChange, onBlur, etc.), but the schema change itself acts as an implicit trigger.

The normalizeSchema utility wraps both Yup and Zod schemas into a common interface that VeeValidate's core validation engine consumes. This abstraction is why the behavior is identical regardless of which schema library you use.

Critical Requirements

• Reactivity is mandatory: validationSchema must be a ref, computed, or reactive object property. A plain object swap will not trigger re-validation because Vue cannot detect the change.
• No explicit validate() or resetForm() needed: The watcher handles it. Call validate() manually only if you need synchronous results immediately after the swap.

Caveats to Expect

• Touched/dirty state persists: Schema replacement re-evaluates errors only. Fields that were touched remain touched; fields that were dirty remain dirty.
• New required fields error immediately: If the new schema adds required fields that have no value, they will show errors right away—even if the user hasn't interacted with them.
• Async validation window: Custom async validations from the previous schema may leave stale errors briefly until the new schema's async rules resolve.
• Zod uses safeParse internally: Ensure your Zod schemas behave as expected under safeParse (no throwing).

Minimal Verification

<script setup>
import { useForm } from 'vee-validate'
import * as yup from 'yup'
import { ref } from 'vue'

const schema = ref(yup.object().shape({ email: yup.string().email().required() }))
const { errors, validate } = useForm({ validationSchema: schema })

function swapSchema() {
  schema.value = yup.object().shape({}) // remove field
  // errors.email clears automatically
}
</script>

Observe errors in Vue DevTools before and after calling swapSchema() without invoking validate(). Repeat with z.object({...}) to confirm parity.

One Diagnostic Detail

Are you passing validationSchema as a ref/computed or as a plain object? This determines whether the automatic re-validation fires at all.