impossible to set setFieldError on array fields with latest toTypedSchema

[hi-reeve]

What happened?

from this issue

we can setFieldError on useFieldArray like this setFieldError('users[0].name','error message')
but with the latest toTypedSchema the autocomplete of setFieldError is only reading the root property of the validationSchema

Reproduction steps

1. create a validationSchema with array type
2. try to manually set the object of the array type schema ex: users[0].name
3. typescript will yell at you
   ...

Version

Vue.js 3.x and vee-validate 4.x

What browsers are you seeing the problem on?

• Firefox
• Chrome
• Safari
• Microsoft Edge

Relevant log output

-

Demo link

https://stackblitz.com/edit/vitejs-vite-1kvon3?file=src/App.vue

Code of Conduct

• I agree to follow this project's Code of Conduct

[logaretm]

This is tricky to have since it means we need to have the field paths as recursive TS literal type instead of keys of the given object.

But I believe it is a worthwhile enhancement and will remove all weirdness about setting fields and errors values for nested paths.

I will be working on this for the next minor release.

[hi-reeve]

This is tricky to have since it means we need to have the field paths as recursive TS literal type instead of keys of the given object.

But I believe it is a worthwhile enhancement and will remove all weirdness about setting fields and errors values for nested paths.

I will be working on this for the next minor release.

thanks!
right now my workaround is only to do @ts-expect-error directive but i believe this is not a good solution

[hi-reeve]

stumble upon this today, this also will be a problem if the key of the validation schema is dynamic and not defined before.

[hi-reeve]

@logaretm this breaks in the new version. the value is set to array.index.key not to the correct index

[logaretm]

@hi-reeve What do you mean? Don't think something was changed related to this since the fix. Got an example?

[hi-reeve]

@hi-reeve What do you mean? Don't think something was changed related to this since the fix. Got an example?

take a look at the current version
https://stackblitz.com/edit/vitejs-vite-ynk5jg?file=src%2FApp.vue

when setting setFieldError using the supposed to be method field.${idx}.property it doesn't correctly set the error for the field

and if we set the name of the field to be field.${idx}.property
doesn't seem the validation is working either

the vue devtools detecting if we name the field format as field.${idx}.property is not the same as field[${idx}].property isn't this supposed to be the same? it read the same on version 4.9.x

so with this, if we set the error using the format field.idx.property the validation will always be false

[hi-reeve]

@logaretm

[logaretm]

Right, seems like paths should be normalized to use one syntax over the other. I will try to look into what we need to do here.

[hi-reeve]

Right, seems like paths should be normalized to use one syntax over the other. I will try to look into what we need to do here.

thankyou. and regarding setting this field to field.idx.property yup does not read this as an array validation but a normal object because the output was field.0.property not field[0].property

[logaretm]

Right, that shouldn't be an issue with the fix since .0. and [0] are exactly the same thing to vee-validate. I realize that means objects with 1 or numeric keys are not possible but that was always intended, this may change in v5 but for now both should refer to the same path.

There might be some bugs around this area but thanks to you reporting this, it should be more consistent now. I will tag a release shortly with the fix.

[hi-reeve]

Right, that shouldn't be an issue with the fix since .0. and [0] are exactly the same thing to vee-validate. I realize that means objects with 1 or numeric keys are not possible but that was always intended, this may change in v5 but for now both should refer to the same path.

There might be some bugs around this area but thanks to you reporting this, it should be more consistent now. I will tag a release shortly with the fix.

thankyou for the quick fix! great job!