Security News
Fluent Assertions Faces Backlash After Abandoning Open Source Licensing
Fluent Assertions is facing backlash after dropping the Apache license for a commercial model, leaving users blindsided and questioning contributor rights.
@vee-validate/zod
Advanced tools
Official vee-validate integration with Zod schema validation
Zod is an excellent library for value validation which mirrors static typing APIs.
In their own words it is a:
TypeScript-first schema validation with static type inference
You can use zod as a typed schema with the @vee-validate/zod
package:
# npm
npm install @vee-validate/zod
# yarn
yarn add @vee-validate/zod
# pnpm
pnpm add @vee-validate/zod
The @vee-valdiate/zod
package exposes a toTypedSchema
function that accepts any zod schema. Which then you can pass along to validationSchema
option on useForm
.
This makes the form values and submitted values typed automatically and caters for both input and output types of that schema.
import { useForm } from 'vee-validate';
import { object, string } from 'zod';
import { toTypedSchema } from '@vee-validate/zod';
const { values, handleSubmit } = useForm({
validationSchema: toTypedSchema(
object({
email: string().min(1, 'required'),
password: string().min(1, 'required'),
name: string().optional(),
})
),
});
// ❌ Type error, which means `values` is type-safe
values.email.endsWith('@gmail.com');
handleSubmit(submitted => {
// No errors, because email is required!
submitted.email.endsWith('@gmail.com');
// ❌ Type error, because `name` is not required so it could be undefined
// Means that your fields are now type safe!
submitted.name.length;
});
You can also define default values on your zod schema directly and it will be picked up by the form:
import { useForm } from 'vee-validate';
import { object, string } from 'zod';
import { toTypedSchema } from '@vee-validate/zod';
const { values, handleSubmit } = useForm({
validationSchema: toTypedSchema(
object({
email: string().default('something@email.com'),
password: string().default(''),
})
),
});
Your initial values will be using the schema defaults, and also the defaults will be used if the values submitted is missing these fields.
You can also define preprocessors to cast your fields before submission:
import { useForm } from 'vee-validate';
import { object, number, preprocess } from 'zod';
import { toTypedSchema } from '@vee-validate/zod';
const { values, handleSubmit } = useForm({
validationSchema: toTypedSchema(
object({
age: preprocess(val => Number(val), number()),
})
),
});
// typed as `unknown` since the source value can be anything
values.age;
handleSubmit(submitted => {
// will be typed as number because zod made sure it is!
values.age;
});
4.15.0
FAQs
vee-validate integration with zod schema validation
We found that @vee-validate/zod demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Fluent Assertions is facing backlash after dropping the Apache license for a commercial model, leaving users blindsided and questioning contributor rights.
Research
Security News
Socket researchers uncover the risks of a malicious Python package targeting Discord developers.
Security News
The UK is proposing a bold ban on ransomware payments by public entities to disrupt cybercrime, protect critical services, and lead global cybersecurity efforts.