[0.5.x] Async validate

[timacdonald]

This PR introduces the ability to respond to individual validation requests via a callback.

This is the most requested feature of Precognition.

• onValidate callback or async validate (reopen) #59
• onValidate Callback or async validate #56
• async validate() #51
• Trigger validation immediately if necessary #83
• Validate more than one field #47
• support async validate #66
• Async validate #67

The validate method now accepts a second parameter that can accept configuration.

<TextInput
    v-model="form.name"
    @change="form.validate('name', {
        onSuccess: () => /* ... */,
        onValidationError: () => /* .. */,
    })"
/>

This is also useful when building a wizard. You may call validate without any input name to and progress to the next page on success or show an alert on failure.

<Button 
    @click="form.touch(['name', 'email', 'address', 'phone']).validate({
        onSuccess: () => nextPage(),
        onValidationError: () => notify('You have validation errors'),
    })"
>
    Next
</Button>

The local configuration options will always overwrite the global configuration (or merge intelligently when applicable).

const form = useForm('post', '/register', { ... }, {
    onFinish: () => console.log('global config'),
})

form.validate()
// global config

form.validate({
    onFinish: () => console.log('local config'),
})
// local config

[redwanjamous]

Hey @timacdonald , thanks for the hard work!
Can you please make sure Inertia is covered in this?
In the original PR (#66 ), react-inertia and vue-inertia packages were not covered.
I tried to cover them in this PR

[timacdonald]

It will cover all packages. Still a WIP.

[djurovicigoor]

Hello,

Is there any progress on this? It's been almost a month since this has been in Draft. It would be very helpful to have this feature implemented. I have an application in production that isn't working perfectly because I am waiting on this feature.

Thank you.

[timacdonald]

@djurovicigoor, still working on this, just had a few other things that were a higher priority.

This one is back on my list and being pushed forward.

[timacdonald]

Could we resolve this and then never resolve the latestPromise instead of throwing an error?

[robdekort]

I'm wondering if this will fix #73 as well. This seems very much related.

[timacdonald]

This is now handled in the before callback, which makes better sense to co-locate things.

[valh1996]

Hi @timacdonald, I just closed my feature request #83 because it seems related.

Do you know when it will be online please?

[jamesparkes]

nice work! i've been sitting on this PR for a while. we cannot wait to use it. our team will be leveraging that callback on our app's multistep forms! previously, we'd been 🧀 ing a timeout since the callback didn't exist yet.

[mreduar]

Thank you @timacdonald 🙏