Regle validation is immediate unlike Vuelidate which is after submit

[mrleblanc101]

Not sure if it's a bug, or a documentation issue, but I haven't seen it mentioned inside the Vuelidate migration guide.

Currently, with Vuelidate, the first validation is only done on form submit, then the errors becomes reactive.

1. Enter value in required field, ok
2. Erase value in required field, ok
3. Submit form shows error, ok
4. Enter value, ok (errors is removed reactively)

But with Vuelidate, the first validation is done as soon as the field become dirty.

1. Enter value in required field, ok
2. Erase value in required field, wrong (shows error)
3. Submit form shows error, ok
4. Enter value, ok (errors is removed reactively)

I tried the rewardEarly modifier, but that's not exactly the same because if I submit the form with an empty required field, it shows the error as expected, if I fill the field, the error will disapear but it won't reappear if i empty the field again.

[mrleblanc101]

Maybe the migration guide should also include this:

-:errors="v$.password.$errors"
+:errors="r$.$errors.password"

[mrleblanc101]

I've tried every combinaison of autoDirty, lazy, rewardearly I could think of

[victorgarciaesgi]

I see, you want a mode where it's autoDirty: true, but only after all the form is touched (or $validate is called) ?

[mrleblanc101]

After $validate is called yes.

That's how vuelidate worked I think ? Unless I was doing something wrong.
So I think it should be documented in the migration guide.
And maybe we should have an option to have the same behavior.

Seems more logical to me than showing an error because the email is invalid while the person is still typing it for example 🤔
This would also match the behavior or backend validation.

[victorgarciaesgi]

By default Vuelidate have autoDirty: false, how you handle the submit is up to you, not Vuelidate, it depends how you handled it using $model, or $touch, etc.
There is a lot of behaviour possible for a form, so there is not "one" good option, juste different modes

[mrleblanc101]

But changing autoDirty: false does not have the same behavior as vuelidate either.
Then, the field show the error on submit yes, but is only revalidated on subsequent submit, not "live".

Here is the behavior I want, this is what I had with vuelidate.

[victorgarciaesgi]

Yeah you want a rewardEarly behaviour then, that will remove error 'live' only after it's touched

[victorgarciaesgi]

But rewardEarly will not show again the error until after submit

[mrleblanc101]

@victorgarciaesgi

But rewardEarly will not show again the error until after submit

Exactly !

That's why I think this slight difference with vuelidate should be documented in the migration guide.

Either Regle behavior should be changed to match how vuelidate worked, or maybe there should be a new option so we can have the old vuelidate behavior.

[mrleblanc101]

@victorgarciaesgi Can we consider this for the roadmap for 1.1 ?

[victorgarciaesgi]

Hey yeah I plan to work on this before 1.1

[IGx89]

Hello! Did this make it into v1.1? We rely on this behavior too in vuelidate. Besides that this library looks perfect, thanks for making this!

[victorgarciaesgi]

Nope! I'll do it for 1.2, I was still turning my head around the behaviour on this one, but this should be simple. Sorry for this!