A3S Form
  • next

      • Development baseline

      The current development baseline includes:

      • Designer, Renderer, and Playground use the published @a3s-lab/ui@0.2.1 contract;
      • field, fieldset, input, select, btn, tabs, accordion, card, app-shell, and workspace-header map to real component DOM;
      • @a3s-lab/form/styles.css keeps the A3S UI-compatible token layer inside Form roots and ships no global preflight;
      • workflow-node configuration has a host-neutral, digest-pinned contract and a tested Dify-like React host;
      • Vue and Web Components forward host errors, locale, read-only state, adapters, and extension registries;
      • every successful plan records Schema Profile 1, unsupported keywords fail with exact paths, and implemented constraints have structural runtime semantics;
      • computed fields use a stable dependency order, bounded calculations, stale-output removal, and an inspectable execution trace;
      • field blur and primary submit support host-owned async validation with cancellation and stable issue mapping;
      • host-owned option sources support declared dependencies, focus triggers, isolated TTL caching, deduplication, cancellation, search, pagination, and accessible failure states;
      • compiled field subscriptions prevent unrelated fields from rerendering, while event and pagination callbacks retain the latest controlled host value;
      • a3s.dev/form-locale-catalog/v1 supplies English and Chinese runtime copy with React, Vue, Web Component, and Designer-preview host overrides;
      • CI benchmarks compile, validation, incremental evaluation, and server rendering at 100, 500, and 1,000 nodes;
      • nested object repeaters provide real row templates, concrete error paths, stable non-persistent runtime identity, host-derived identity, ordering, limits, and responsive rendering;
      • repeated fields support row-scoped calculation, validation, visibility, enablement, and host-owned data-source dependency templates;
      • the Router workflow-node example edits routes as ordinary metadata-free configuration with per-row validation and branch options rather than one raw JSON field;
      • editable data grids render object arrays as semantic tables with controlled row operations, localized headers, and a narrow-container row-card layout;
      • true wizard layouts provide visible-rule branches, page-scoped validation, progress and review UI, earlier-page error recovery, and digest-bound host checkpoints without adding navigation metadata to values;
      • existing a3s-form-* selectors and controlled interfaces remain compatible.

      Read the workflow-node embedding guide for host ownership boundaries, repeatable field groups for object-array authoring and identity, editable data grids for compact table editing, multi-page wizards for branching and checkpoint contracts, Schema Profile 1 for the accepted validation contract, computed rules for derived node parameters, async validation for protected business checks, data sources for dynamic node options, and localization and performance for host copy and runtime budgets. Use the migration checklist before publishing a new digest. These changes remain in next and do not create a new compatibility commitment until released.