Experimenting with zod v4 beta, handleSubmit fails to infer the correct data type.

[semet]

Dear..
Im grateful this awesome library existed. It helps me a lot with may daily life as a coder. However, as a normal Human that always want to try new thing, I come to a simple experiment once the new zod v4 beta is arrived. No user of this awesome library can deny how good these two work with eachother.
During this simple experiment, I notice something like this:

the useForm hook init:

  const formMethods = useForm({
    resolver: zodResolver(companyBankFilterSchema),
    defaultValues: INITIAL_FILTER,
  })

here is my schema using the new zod v4 beta

import { z } from 'zod'

export const companyBankFilterSchema = z.object({
  bank_group_id: z
    .object({
      label: z.string(),
      value: z.string().optional(),
    })
    .optional(),
  bank_id: z
    .object({
      label: z.string(),
      value: z.string().optional(),
    })
    .optional(),
  status: z
    .union([z.literal(1), z.literal(2), z.literal(3)])
    .describe('1: Active 2: Inactive 3: Suspended')
    .optional(),
  bank_category: z.string().optional(),
  active: z.boolean().optional(),
  inactive: z.boolean().optional(),
})

export type TCompanyBankFilter = z.infer<typeof companyBankFilterSchema>

and here is my handleSubmit:

 const { handleSubmit, reset, watch, setValue } = formMethods

  const onSubmit = handleSubmit((data) => {
    resetPagination()
    setFilter(data)
  })

here we can see the data returned by the handleSubmit is of type unknown, whereas in zod v3 it was correctly infered based on the shape of the schema.

Im not really sure is this specific to React Hook Form or related to the Hook Form Resolver package. but i think it will be useful to address it here...

Thank you so much ..

[sheldon-welinga]

For anyone facing this issue, adding the generic inference directly to the useForm hook solved it for me

 const formMethods = useForm<TCompanyBankFilter>({
    resolver: zodResolver(companyBankFilterSchema),
    defaultValues: INITIAL_FILTER,
  })