Support ref (and possibly computed) about vuelidate

[VividLemon]

const count = ref(0);

const newRules = {
  value: {
    maxLength: maxLength(5)
  }
}

const newerV$ = useVuelidate(newRules, count);

Should be changed to

const count = ref(0);

const newRules = {
  count: {
    maxLength: maxLength(5)
  }
}

const newerV$ = useVuelidate(newRules, { count });

The usage is actually noted at https://vuelidate-next.netlify.app/advanced_usage.html#using-an-object-of-refs , although, I am not a particular fan of writing it like this.

In my personal option, the parameter positions of rules/values is backwards. If it was created to be values/rules , then you could define your values object (or lets say also allowing a direct ref, rather than being forced into always needing an object), then you could define your rules with intellisense. I find myself often times working backwards when using the current api. Although, this doesn't really pertain to this issue

[CaseyHofland]

Thanks, I understand now.

You raise a good point with intellisense though. Vuelidate is great once it works, but I’ve already lost hours of time due to the intellisense issue alone. When it doesn’t work, I’m frantically trying to change everything until I realize oep, someone changed a type somewhere but everything still build correctly and nobody realized they needed to change the vuelidate schema. It’s incredibly frustrating.

If intellisense will not work with vuelidate, I would at least want it to throw an error so I can debug in the console. Right now it’s not giving me anything. It would have likely helped me out with this problem, too.