fe-zod-form

Generate Zod schemas for multi-step forms by creating individual step schemas and exporting inferred types into features/<feature>/logic/ files with a .schema.ts suffix. This approach uses standardSchemaResolver to validate each step independently via trigger(fields).

Cross-field validation in Zod is best set up using refine or superRefine methods within your schema. This ensures complex conditional rules are evaluated properly when integrated with react-hook-form using standardSchemaResolver and onChange mode.

react-hook-form works with standardSchemaResolver to handle file uploads by defining the file validation rules directly in your Zod schema. This integration maintains type safety and validates inputs correctly during create and edit flows.

You should avoid zodResolver and inline schemas because they break project alignment and maintainability. Using standardSchemaResolver with dedicated .schema.ts files ensures consistent validation, proper type inference, and correct file placement for single-step and multi-step forms.

Scaffold a react-hook-form component using Zod by wrapping inputs in FormProvider, configuring standardSchemaResolver, setting mode to onChange, and defining defaultValues. This structure uniformly supports both create and edit data flows.

You can use standard-schema for partial form validation in wizard steps by exporting individual step schemas and applying trigger(fields) from react-hook-form. This validates only the active step fields before allowing the user to proceed.