VeeValidate 4.x nested error mapping: flat vs nested structure limits
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
veevalidate