put a warning in the docs about using zod refine() with vee-validate

[cinderisles]

I started using zod after finding out about it from the vee-validate docs, but now I regret it, because I didn't know that zod's refine() would be pretty much incompatible with a form validation library like this

It works great with vee-validate for simple schemas, but it's completely useless for anything complex

There is good discussion already in these issues, so I don't feel the need to repeat everything.

• Can't get zod superRefine / refine to work on zod.object() . #4208
• Refine validations on object definitions don't get triggered until all fields in the object exist. colinhacks/zod#479
• [Feature request] An option to always execute refines even if parse failed, or workaround colinhacks/zod#2524

I understand that this isn't an issue with vee-validate

What do you think of adding a warning to the docs in certain places where zod is mentioned, explaining that refine() wont work as expected? I can probably make a PR for it if you're too busy, but just wanted to get feedback first

---

since the zod devs have been quiet about this issue, I am currently having to migrate my schemas used with vee-validate to yup, in hopes that the custom validators work better. i might even just use vee-validate rules instead of yup

[logaretm]

That makes sense, I have added it to parts of the docs where zod schema is used as a form schema. Thanks!

[philipimperato]

This should be way more prominent. It's borderline incompatible with vee-validate. You can't use the validationSchema without weird, buggy quirks.