vee-validate · Issues· 172 open

Zod 4 support

Is this project still maintained?

`toTypedSchema` initializes nested object fields as `{field: undefined}` instead of `undefined` when root schema is `ZodObject`, but not when it is `ZodEffects`

union errors aren't handled properly with Vee-Validate 4 + Zod 4

Validation results for not-rendered fields are always present

Deeply nested array form prunes array attributes, when bound to vee-validate useField and used with 'replace' from useFieldArray

a top-level array as initialValue is corrupted

v4: get an error "Invalid key: Expected "address" but received undefined" if field is object in valibot schema

Breaking Change in `useField` Behavior After v4.11.8 - meta object no longer syncs

ALL your demos do NOT work on the website

missing translation for url

v5: FieldArray's push/remove should set form as touched

Vee validate zod schema defaultValue

Add defineArrayField for type-safe array field management (mirrors defineField pattern)

PathValue returns `never` for bracket notation array paths like `items[0].name`