💣 Breaking Changes
Deprecated reactive initial values #4402 (bbecc97)
Initial values can no longer be reactive since they did not serve any purpose for being so. The recommended API for setting async initial values is by explicitly calling resetForm
.
🆕 defineField
API #4497
This is a new function available on useForm
and is meant to replace useFieldModel
, defineInputBinds
and defineComponentBinds
by building upon and improving those APIs.
<script setup>
import { useForm } from 'vee-validate';
const { defineField, errors } = useForm({
validationSchema: schema,
validateOnMount: true,
});
const [email, emalProps] = defineField('email', { validateOnModelUpdate: true });
const [password, pwProps] = defineField('password', { validateOnModelUpdate: true });
</script>
<template>
<input v-model="email" v-bind="emailProps" />
<span>{{ errors.email }}</span>
<input v-model="password" v-bind="pwProps" />
<span>{{ errors.password }}</span>
</div>
</template>
The docs have been updated to reflect using this new API instead of the deprecated ones. The old ones will continue to work till they get removed in next minor releases.
🆕 meta.required
Added support for meta.required
state for Typed Schemas only.
That means if you are using toTypedSchema
helper with either Yup, Zod, Valibot, or Global rules then it should be automatically done for you. This is a new experimental feature and may not work well with conditional schemas or dynamic ones.
For more info check the live demo link here.
🆕 DX improvements
- feat: add label support to defineField #4530 (f9a9584)
- feat(DX): allow getters for field arrays paths (95b701f)