useVuelidate doesn't signal that it unwraps the validation ref when used in a template about vuelidate

[VividLemon]

Add a <p v-if="v$.name> element

This doesn't have an issue. So, I'm confused about what this is exactly referring to.

However, what does error is the issue of

export interface ErrorObject {
  readonly $propertyPath: string
  readonly $property: string
  readonly $validator: string
  readonly $message: string | Ref<string>
  readonly $params: object
  readonly $pending: boolean
  readonly $response: any,
  readonly $uid: string,
}

readonly $message: string | Ref<string>

The issue with doing something like v$.name.$errors.map((el) => el.$message) is problematic. the nested Ref of $message is not going to be unwrapped -- either through template, another ref, or reactive (https://vuejs.org/guide/essentials/reactivity-fundamentals.html#caveat-in-arrays-and-collections) This leads to the issue with the Vuetify mentioned issue.

My best advice in this case would be to remove the Ref from that type and ensure that the $errors object is either a ref or reactive already -- no use in wrapping it (I'm pretty sure!)

This particular issue I'm noting is not directly related to the original issue. But its a large issue for Vuetify apps! I am fully willing to make any modifications to the lib, but I need to know if its okay, considering it could be a breaking-change bug

[GalacticHypernova]

My best advice in this case would be to remove the Ref from that type

The issue is trying to access any property results in that error, which is just not great for DX.