formvuelate@4.3.0

Minor Changes

• d8308ca: Add read-only schema elements. Set readonly: true on any element and FormVueLate will render its component and hand it the whole form model to read, but it will never wire v-model, so the element can't write a value back or show up in your form output. It's a clean way to drop group labels, headings, or live summaries into a schema without treating them as fields. Read-only elements are also skipped by the vee-validate plugin, so they're never registered for validation.

@formvuelate/plugin-vee-validate@4.3.0

Minor Changes

• d8308ca: Add read-only schema elements. Set readonly: true on any element and FormVueLate will render its component and hand it the whole form model to read, but it will never wire v-model, so the element can't write a value back or show up in your form output. It's a clean way to drop group labels, headings, or live summaries into a schema without treating them as fields. Read-only elements are also skipped by the vee-validate plugin, so they're never registered for validation.

@formvuelate/plugin-lookup@4.3.0

@formvuelate/plugin-lookup@4.3.0

formvuelate@4.2.0

Minor Changes

• a6e6bd0: Expose the form-level validation state outside SchemaForm. The vee-validate plugin now emits an update:validation event (usable as v-model:validation) carrying the same errors, values, isSubmitting, submitCount and meta object that the #beforeForm / #afterForm slot prop already provides. The state is seeded on mount and refreshed on every change, and only the root schema form emits it so nested schemas stay quiet.

  To support this, plugins can now extend the generated component's declared events through a new extendEmits helper passed alongside extendSchemaFormProps to a plugin's extend hook.

@formvuelate/plugin-vee-validate@4.2.0

Minor Changes

• a6e6bd0: Expose the form-level validation state outside SchemaForm. The vee-validate plugin now emits an update:validation event (usable as v-model:validation) carrying the same errors, values, isSubmitting, submitCount and meta object that the #beforeForm / #afterForm slot prop already provides. The state is seeded on mount and refreshed on every change, and only the root schema form emits it so nested schemas stay quiet.

  To support this, plugins can now extend the generated component's declared events through a new extendEmits helper passed alongside extendSchemaFormProps to a plugin's extend hook.

@formvuelate/plugin-lookup@4.2.0

@formvuelate/plugin-lookup@4.2.0

formvuelate@4.1.0

Minor Changes

• 0d00ac5: Add SchemaArray, a core field for repeatable/variable-length lists. Declare it directly in your schema ({ friends: { component: SchemaArray, items } }) anywhere in the schema, including dynamic schemas; items can be a group of fields (array of objects) or a single field (array of scalars), and arrays can nest. It owns the array as a real array in the model and stays strictly UI-agnostic, shipping no markup. Add/remove/reorder controls are your own components declared via after (per row) and append (once), which emit their intent (add/remove/move) for SchemaArray to perform. min/max are exposed as canAdd/canRemove to those controls.

  Also fixes a process is not defined crash when FormVueLate runs in the browser (the dev-only warnings now guard typeof process).

@formvuelate/plugin-vee-validate@4.1.0

@formvuelate/plugin-vee-validate@4.1.0

@formvuelate/plugin-lookup@4.1.0

@formvuelate/plugin-lookup@4.1.0

formvuelate@4.0.1

Patch Changes

• bdabdea: Dev-only guard in useSchemaForm that emits a clear, actionable FormVueLate warning (pointing at the docs) when called without an active component instance. Matches the existing process.env/FormVueLate: convention in SchemaFormFactory.js.

  Refs #302