How can one get localized custom error messages?

[Winston-Guess]

In version 3 you could get a custom message for each specific validation rule error for a specific field with:

:rules="required|anotherRule"
:customMessages="{
  required: `This error message overrides standard 'required' error message `,
  anotherRule: `another custom message for 'anotherRule'`,
}"

However, there seems to be no option for doing this on <Field /> or on <ErrorMessage />. I also cannot get this working without writing some very dodgy code because <Form />, <Field /> and <ErrorMessage /> do not return any reference to the rule that the current error is stemming from.

It seems very strange to me that (1.) this feature is not replicated in v4 and (2.) that <Field /> and <ErrorMessage /> doesn't reference the errors' originating rule. I'm not sure why vee-validate v4 has gotten rid of so many features that made previous versions so easy/powerful to use (for another example mode="eager|lazy|etc").

[logaretm]

(1.) this feature is not replicated in v4

In v4, vee-validate was re-worked to include 3rd party validation support without the need for global registration. That meant that vee-validate could no longer have special treatment for individual rules.

I'm not sure why vee-validate v4 has gotten rid of so many features that made previous versions so easy/powerful

Because the composition API didn't exist before, which means that features that was very hard to implement like interaction modes was no longer required to be built-in. I realize this is easily said than done especially when there is no migration guide or examples on the missing features. I will try to add what I can to the current docs.

at the moment there is no straightforward way to do this at the field level, you may consider using the i18n dictionary API to achieve this but you need to call it in your script section.

[Winston-Guess]

Thank you for your response. Could we not then at least get <Form />, <Field /> and <ErrorMessage /> to return a reference to the rule that the current error is stemming from?

In terms of the missing interaction modes: I'm currently porting my app over to vue3 but not rewriting everything with the composition API unless I need to. So I'm now sitting in a bit of a difficult place. I can't yet move to using the composition API across the board because it would have been a hard sell to our stakeholders to completely rewrite every component that used validation (it would probably be 80% of the app). However, I have to move to using v4.

Anyways, that's my problem. I did look at using other validation systems but I don't like the other implementations. So I'll have to go with some hack until we do a proper rewrite.