fix(zod): update return type in zodResolver to use z.input instead of…

[diegotraid]

Resolves #743

For the function zodResolver to return a type compatible with react-hook-form, it must return Resolver<z.input<typeof schema>> instead of Resolver<z.infer<typeof schema>>.

[controversial]

Is it possible for useForm to also infer the TTransformedValues parameter from the Resolver? or can useForm only pick up the TFieldValues input shape from the Resolver?

[diegotraid]

Is it possible for useForm to also infer the TTransformedValues parameter from the Resolver? or can useForm only pick up the TFieldValues input shape from the Resolver?

That, I think, it's the main issue here.
I think resolvers doesn't take transformed values into consideration:

export type Resolver<TFieldValues extends FieldValues = FieldValues, TContext = any>

While useForm does:
useForm<TFieldValues extends FieldValues = FieldValues, TContext = any, TTransformedValues extends FieldValues | undefined = undefined>

[controversial]

At the very least, this PR will be an improvement over the current situation

[diegotraid]

Waiting for react-hook-form/react-hook-form#11951 to be merged into master to provide a more correct solution to this.

[controversial]

That PR was merged into react-hook-form’s main 3 days ago I believe

[jorisre]

Hi everyone,

Thank you for your contributions. A PR was merged a few days ago, but the work is still ongoing. I'm currently working on RHF and resolvers to implement type inference, (Input vs. Output/Transformed Values from the schema).

Unfortunately, while this PR resolves one issue, it has created another. At this point, both libraries (RHF & resolvers) need to evolve.

Please keep an eye out for upcoming PRs—your reviews and feedback will be greatly appreciated.

[controversial]

Thanks for your hard work @jorisre!

[diegotraid]

Closing since this is being resolved with PR #753