VeeValidate v4 field-level validateOnValueUpdate versus global configure() defaults
0 reputation · 14 Jul 2023, 22:00 UTC
VeeValidate v4 field-level validateOnValueUpdate versus global configure() defaults
The goal is to determine whether a field-level validateOnValueUpdate option replaces or merges with the equivalent key set globally through configure() in VeeValidate v4 on Vue 3, particularly when a field value changes programmatically.
VeeValidate v4 replaces v3's ValidationProvider and ValidationObserver with composition functions, and global trigger defaults are set through configure(). Field-level options generally take precedence, but the documented behavior for validateOnValueUpdate during programmatic assignments is unclear, and TypeScript types may not reflect the actual merge strategy.
Which value wins when both global and field-level validateOnValueUpdate are defined? Does programmatic value assignment count as a value update for trigger purposes? Is there a reliable way to inspect the resolved trigger configuration before mount?
veevalidate