VeeValidate 4.x nested error mapping limits

VeeValidate 4.x nested error mapping: flat vs nested structure limits

0 reputation · 11 Dec 2023, 18:42 UTC

116.4K views0

Goal

Determine whether VeeValidate 4.x should automatically transform dot‑notation validation errors into a nested error object or keep a flat errors map.

Constraints

The library currently stores nested field errors under flattened keys (e.g., profile.email) while the form model remains hierarchical. Documentation does not specify a default conversion, and custom renderers are required for deep structures.

Open questions

Is there a configuration flag or provider that enables automatic nesting of error keys?
What are the implications for schema‑based validation when optional nested objects are omitted?
How does the global validation context interact with scoped forms in this scenario?

1,361 following

Keep exploring this topic

VeeValidate async cross-field validation re-trigger behavior

VeeValidate lacks documented constraints on when async cross-field validations re-run after dependency changes, leaving debounce, cancellation, and re-trigger timing to application code with version-dependent behavior.

veevalidate async validation rejection not reflected in UI after initial mount

Investigation of veevalidate's async validation promise rejection and automatic UI update behavior during initial mount

Limits of ValidationProvider error clearance when rules prop changes in veevalidate v4

When the rules prop of a ValidationProvider component changes in veevalidate v4, existing validation errors are not automatically cleared.

Async validation race condition with validateOnMount in vee-validate v4

vee-validate v4 lacks a built-in cancellation mechanism for async validation when validateOnMount fires rapidly. Stale responses can overwrite newer error states. Seeking a pattern to guarantee only the latest validation cycle updates the field.

VeeValidate 4.x nested error mapping: flat vs nested structure limits

Goal

Constraints

Open questions

0 answers

Your perspective belongs here.

0 question comments