Abdelrahman Awad

Add `useField('myArray')` after the form. ```ts const form = useForm({ validationSchema: { myArray: array().min(1), }, initialValues: { myArray: [], // Invalid array }, validateOnMount: false, // No error should appear...

This would be solved by a change I suggested #4630, closing in favor of tracking it in that one. In this issue `useField` and `useFieldArray` are being confused for vee-validate...

The `valid` flag is independent from the `errors` existence, because a silent validation is run initially. Do you mind creating an example for this?

You are right that's a perfectly valid way to think about it but from usability perspective, let's say you want to disable the submit until the form is valid. Now...

We have a vue-devtools plugin that gets auto-installed it does help with cases of hidden errors or why a form isn't submitting or why it is valid. But it doesn't...

Thanks for reporting this and the issue reproduction. `initialValues` should not probably be treated as reactive because it only affects untouched fields. I should probably deprecate this and document it....

Hello there, I'm planning on some improvements for multistep forms for `4.9` or `4.10` depending on my release schedule. But it could be simple enough for a quick release but...

I see, this could make sense in the improvement that i'm considering for multistep forms like meta for each step and so on. But long way to get there as...

Not possible at the moment. However, I don't think it needs much work to get it working. I will see what I can do.

@cas-technology Some rules do receive `false` as an argument, so turning them off with falsy values is risky.