vorm-vue v1.2.5

vorm-vue

1.2.5

Patch Changes

• #54 9668bec Thanks @Flo0806! - fix: validate() now validates repeater subfields correctly
  • validate() uses expandSchema to include repeater fields (e.g., projects[0].name)
  • isValid computed now considers repeater subfields
  • Added tests for validate() with repeater fields

1.2.4

Patch Changes

• #52 13d340d Thanks @Flo0806! - fix: skip validation for hidden fields (showIf condition false)
  • Hidden fields are no longer validated and don't block form submission
  • Errors are automatically cleared when a field becomes hidden
  • isValid computed only considers visible fields
  • Added resolveRelativePath to pathHelpers for shared use

1.2.3

Patch Changes

• #50 f73fdd4 Thanks @Flo0806! - Fix validation for fields inside repeaters. validateFieldByName now correctly validates nested fields like projects[0].url by using the expanded schema. Added tests for repeater and nested repeater validation.

1.2.2

Patch Changes

• #48 aeb8750 Thanks @Flo0806! - Fix schema classes property not being applied to label, help, and outer elements in VormField component. Previously only classes.input was working, now all class properties (outer, label, input, help) are properly applied alongside the default vorm-* classes.

1.2.1

Patch Changes

• #46 6845275 Thanks @Flo0806! - fix: improve input performance with many fields
  • Add internal VormField component for isolated reactivity per field
  • Each field now has its own component boundary, preventing re-renders of all fields when one changes
  • Typing in forms with hundreds of fields is now smooth and responsive
  • No API changes - this is an internal optimization

1.2.0

Minor Changes

• #40 cf4eb54 Thanks @Flo0806! - Make disabled property reactive with function support

  • Added ReactiveBoolean type for reactive boolean properties
  • Extended disabled in VormFieldSchema to accept functions with FormContext
  • disabled now supports: boolean, Ref<boolean>, ComputedRef<boolean>, () => boolean, (ctx: FormContext) => boolean
  • AutoVorm resolves disabled reactively and passes it to slot bindings
  • bindField() now includes disabled in its return value

  Example:

  {
    name: 'submit',
    disabled: (ctx) => !ctx.formData.agreeToTerms || !ctx.isValid
  }

• #37 d7ba028 Thanks @Flo0806! - Improve developer experience with reactive errors and resolved slot props

  • vorm.errors is now a reactive object - access errors directly with vorm.errors.email instead of vorm.errors.value.email
  • AutoVorm slot props now receive resolved strings for label, placeholder, and helpText instead of ReactiveString types
  • Full i18n reactivity maintained - dynamic placeholders and labels update reactively when form data or locale changes

• #39 9f7c002 Thanks @Flo0806! - Add schema options and bindField for custom component support

  • Added options field to VormFieldSchema for select/radio/autocomplete fields
  • Extended Option type with custom data support ([key: string]: any)
  • Added ReactiveOptions type (static array, Ref, Computed, Function, Async)
  • Added getFieldOptions() helper for reactive option access
  • Added bindField() method for easy custom component binding
  • AutoVorm wrapper-slots now provide modelValue, items, options, error, errorMessages, onUpdate:modelValue
  • Full backward compatibility with fieldOptionsMap

Patch Changes

• #41 58bf497 Thanks @Flo0806! - Fix affects cascade: clear errors on affected fields when source validation passes

  When a field with affects array passes validation, the affected fields are now
  re-validated to clear any errors that were propagated from the source field.

1.1.3

Patch Changes

• #32 c3ddec1 Thanks @Flo0806! - fix(vorm-vue): isValid now correctly handles fields without validation rules. Fields without validation are now considered valid by default, allowing isValid to return true when all fields with validation rules have been validated and have no errors.

1.1.2

Patch Changes

• #30 99c68d7 Thanks @Flo0806! - Fix isValid computed property to require all fields to be validated

  The isValid property now correctly returns false until ALL fields have been validated, not just at least one field. This fixes the issue where touching a single field would incorrectly mark the entire form as valid.

1.1.1

Patch Changes

• #25 053367b Thanks @Flo0806! - Internal dependency update to align with vorm-nuxt changes

1.1.0

Minor Changes

• #15 290877c Thanks @Flo0806! - Add form-level state flags (isValid, isDirty, isTouched)

  Added reactive computed properties to VormContext for better form state management:

  • isValid: Returns true when form has been validated and has no errors
  • isDirty: Returns true when at least one field has been modified
  • isTouched: Returns true when at least one field has been touched

1.0.2

Patch Changes

• #12 f736430 Thanks @Flo0806! - Fix fieldOptions reactivity and setFormData handling. This patch addresses two critical issues:

  1. Reactivity Fix: Changed fieldOptionsMap from a non-reactive Map to a reactive Record<string, Option[]>. This ensures that select fields properly re-render when options are set via setFormData() or updateField().
  2. setFormData Cleanup: Added proper clearing of old field options before setting new ones, allowing setFormData({}, { fieldOptions: {...} }) to work correctly without explicitly setting field values.

  Breaking Fix: Select fields with dynamic options will now properly update when setFormData() is called, even without explicit field values.

1.0.1

Patch Changes

• #6 3163598 Thanks @Flo0806! - updated readme

1.0.0

Major Changes

• first major version