@vef-framework-react/form-editor 2.19.0 → 2.21.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/cjs/components/checkbox-group-field/index.cjs +1 -1
- package/dist/cjs/components/code-editor/index.cjs +1 -1
- package/dist/cjs/components/mobile/checkbox-group.cjs +1 -1
- package/dist/cjs/components/mobile/date-adapters.cjs +1 -1
- package/dist/cjs/components/mobile/date.cjs +1 -1
- package/dist/cjs/components/mobile/datetime.cjs +1 -1
- package/dist/cjs/components/mobile/radio.cjs +1 -1
- package/dist/cjs/components/mobile/select.cjs +1 -1
- package/dist/cjs/components/mobile/switch.cjs +1 -1
- package/dist/cjs/components/radio-field/index.cjs +1 -1
- package/dist/cjs/components/select-field/index.cjs +1 -1
- package/dist/cjs/components/upload-field/index.cjs +1 -1
- package/dist/cjs/editor/palette/palette-item.cjs +1 -1
- package/dist/cjs/editor/properties/container-properties.cjs +1 -1
- package/dist/cjs/editor/properties/entries/linkage/condition-editor.cjs +1 -1
- package/dist/cjs/editor/properties/entries/linkage/linkage-rules-entry.cjs +1 -1
- package/dist/cjs/editor/properties/entries/linkage/options.cjs +1 -1
- package/dist/cjs/editor/properties/entries/linkage/trigger-editor.cjs +1 -1
- package/dist/cjs/editor/properties/form-variables-panel.cjs +1 -1
- package/dist/cjs/editor/properties/option-editors.cjs +1 -1
- package/dist/cjs/editor/remove-node-confirm.cjs +2 -2
- package/dist/cjs/editor/toolbar/toolbar.cjs +2 -2
- package/dist/cjs/engine/data-source-params.cjs +1 -1
- package/dist/cjs/engine/keys.cjs +1 -1
- package/dist/cjs/engine/linkage/effects.cjs +1 -1
- package/dist/cjs/engine/linkage/evaluator.cjs +1 -1
- package/dist/cjs/engine/linkage/operators.cjs +1 -1
- package/dist/cjs/engine/linkage/shape.cjs +1 -0
- package/dist/cjs/engine/linkage/source-tracking.cjs +1 -1
- package/dist/cjs/engine/linkage/validator.cjs +1 -1
- package/dist/cjs/engine/schema/column-type.cjs +1 -1
- package/dist/cjs/engine/schema/permission-bridge.cjs +1 -1
- package/dist/cjs/engine/schema/removal-impact.cjs +1 -1
- package/dist/cjs/index.cjs +1 -1
- package/dist/cjs/render/chrome/mobile-chrome.cjs +1 -1
- package/dist/cjs/render/chrome/pc-chrome.cjs +1 -1
- package/dist/cjs/render/data-source-context.cjs +0 -0
- package/dist/cjs/render/data-source-param-scope.cjs +1 -1
- package/dist/cjs/render/form-renderer.cjs +1 -1
- package/dist/cjs/render/parts/field-shell.cjs +1 -1
- package/dist/cjs/render/parts/label.cjs +1 -1
- package/dist/cjs/render/parts/option-order.cjs +1 -0
- package/dist/cjs/render/subform-columns.cjs +1 -1
- package/dist/cjs/render/submit.cjs +1 -1
- package/dist/cjs/runtime/effects.cjs +1 -1
- package/dist/cjs/runtime/field-write.cjs +1 -1
- package/dist/cjs/runtime/runtime-state-controller.cjs +1 -1
- package/dist/cjs/store/form-store.cjs +1 -1
- package/dist/es/components/button/index.js +1 -1
- package/dist/es/components/checkbox-group-field/index.js +24 -22
- package/dist/es/components/code-editor/code-editor-input.js +1 -1
- package/dist/es/components/code-editor/index.js +3 -2
- package/dist/es/components/containers/index.js +1 -1
- package/dist/es/components/date-field/index.js +1 -1
- package/dist/es/components/display/index.js +1 -1
- package/dist/es/components/field-entries.js +1 -1
- package/dist/es/components/mobile/alert-block.js +1 -1
- package/dist/es/components/mobile/button.js +1 -1
- package/dist/es/components/mobile/checkbox-group.js +26 -24
- package/dist/es/components/mobile/date-adapters.js +3 -2
- package/dist/es/components/mobile/date.js +36 -34
- package/dist/es/components/mobile/daterange.js +1 -1
- package/dist/es/components/mobile/datetime.js +36 -34
- package/dist/es/components/mobile/definitions.js +1 -1
- package/dist/es/components/mobile/divider.js +1 -1
- package/dist/es/components/mobile/input-cell.js +1 -1
- package/dist/es/components/mobile/number.js +1 -1
- package/dist/es/components/mobile/option-group.js +1 -1
- package/dist/es/components/mobile/paragraph.js +1 -1
- package/dist/es/components/mobile/picker-trigger.js +1 -1
- package/dist/es/components/mobile/radio.js +2 -1
- package/dist/es/components/mobile/scope.js +1 -1
- package/dist/es/components/mobile/select.js +2 -2
- package/dist/es/components/mobile/switch.js +17 -11
- package/dist/es/components/mobile/textarea.js +1 -1
- package/dist/es/components/mobile/textfield.js +1 -1
- package/dist/es/components/mobile/theme.js +1 -1
- package/dist/es/components/number-field/index.js +1 -1
- package/dist/es/components/radio-field/index.js +3 -2
- package/dist/es/components/select-field/index.js +14 -13
- package/dist/es/components/switch-field/index.js +1 -1
- package/dist/es/components/textarea-field/index.js +1 -1
- package/dist/es/components/textfield/index.js +1 -1
- package/dist/es/components/upload-field/index.js +2 -1
- package/dist/es/editor/canvas/canvas-field.js +1 -1
- package/dist/es/editor/canvas/canvas.js +1 -1
- package/dist/es/editor/canvas/container-drag-chip.js +1 -1
- package/dist/es/editor/canvas/drop-indicator.js +1 -1
- package/dist/es/editor/canvas/drop-zones.js +1 -1
- package/dist/es/editor/canvas/json-split-view.js +1 -1
- package/dist/es/editor/canvas/mobile-seed-state.js +1 -1
- package/dist/es/editor/canvas/phone-frame.js +1 -1
- package/dist/es/editor/canvas/subform-column-eligibility.js +1 -1
- package/dist/es/editor/canvas/subform-table-cell.js +1 -1
- package/dist/es/editor/canvas/use-scroll-selection-into-view.js +1 -1
- package/dist/es/editor/context-sources.js +1 -1
- package/dist/es/editor/dnd.js +1 -1
- package/dist/es/editor/editor-layout-context.js +1 -1
- package/dist/es/editor/footer/footer.js +1 -1
- package/dist/es/editor/form-config/form-basics-tab.js +1 -1
- package/dist/es/editor/form-config/form-config-drawer.js +1 -1
- package/dist/es/editor/form-config/linkage-overview.js +1 -1
- package/dist/es/editor/form-config/outline-tab.js +1 -1
- package/dist/es/editor/form-editor.js +1 -1
- package/dist/es/editor/palette/field-groups.js +1 -1
- package/dist/es/editor/palette/palette-group.js +1 -1
- package/dist/es/editor/palette/palette-item.js +71 -70
- package/dist/es/editor/palette/palette-panel.js +1 -1
- package/dist/es/editor/preview-effects.js +1 -1
- package/dist/es/editor/preview-runtime-context.js +1 -1
- package/dist/es/editor/properties/block-layout-section.js +1 -1
- package/dist/es/editor/properties/container-properties.js +198 -200
- package/dist/es/editor/properties/dynamic-value-editor.js +1 -1
- package/dist/es/editor/properties/entries/built-ins.js +1 -1
- package/dist/es/editor/properties/entries/checkbox-entry.js +1 -1
- package/dist/es/editor/properties/entries/coerce.js +1 -1
- package/dist/es/editor/properties/entries/entry-field.js +1 -1
- package/dist/es/editor/properties/entries/icon-entry.js +1 -1
- package/dist/es/editor/properties/entries/index.js +1 -1
- package/dist/es/editor/properties/entries/key-entry.js +1 -1
- package/dist/es/editor/properties/entries/linkage/action-editor.js +1 -1
- package/dist/es/editor/properties/entries/linkage/actions-editor.js +1 -1
- package/dist/es/editor/properties/entries/linkage/condition-editor.js +55 -55
- package/dist/es/editor/properties/entries/linkage/container-linkage-section.js +1 -1
- package/dist/es/editor/properties/entries/linkage/expression-input.js +1 -1
- package/dist/es/editor/properties/entries/linkage/index.js +1 -1
- package/dist/es/editor/properties/entries/linkage/linkage-rules-entry.js +43 -42
- package/dist/es/editor/properties/entries/linkage/mutators.js +1 -1
- package/dist/es/editor/properties/entries/linkage/options.js +5 -2
- package/dist/es/editor/properties/entries/linkage/rule-diagnostics.js +1 -1
- package/dist/es/editor/properties/entries/linkage/rule-list-editor.js +1 -1
- package/dist/es/editor/properties/entries/linkage/styles.js +1 -1
- package/dist/es/editor/properties/entries/linkage/trigger-editor.js +29 -29
- package/dist/es/editor/properties/entries/linkage/use-linkage-editor-model.js +1 -1
- package/dist/es/editor/properties/entries/linkage/use-stable-options.js +1 -1
- package/dist/es/editor/properties/entries/number-entry.js +1 -1
- package/dist/es/editor/properties/entries/options-source/index.js +1 -1
- package/dist/es/editor/properties/entries/options-source/source-mutators.js +1 -1
- package/dist/es/editor/properties/entries/select-entry.js +1 -1
- package/dist/es/editor/properties/entries/text-entry.js +1 -1
- package/dist/es/editor/properties/form-data-sources-panel.js +1 -1
- package/dist/es/editor/properties/form-linkage-panel.js +1 -1
- package/dist/es/editor/properties/form-variables-panel.js +68 -67
- package/dist/es/editor/properties/option-editors.js +102 -85
- package/dist/es/editor/properties/panel-header.js +1 -1
- package/dist/es/editor/properties/properties-empty.js +1 -1
- package/dist/es/editor/properties/properties-header.js +1 -1
- package/dist/es/editor/properties/properties-panel.js +1 -1
- package/dist/es/editor/properties/properties-provider.js +1 -1
- package/dist/es/editor/properties/properties-tabs.js +1 -1
- package/dist/es/editor/properties/use-confirmable-kind-switch.js +1 -1
- package/dist/es/editor/remove-node-confirm.js +36 -29
- package/dist/es/editor/schema-apply.js +1 -1
- package/dist/es/editor/styles.js +1 -1
- package/dist/es/editor/toolbar/notify.js +1 -1
- package/dist/es/editor/toolbar/schema-io.js +1 -1
- package/dist/es/editor/toolbar/toolbar.js +169 -168
- package/dist/es/editor/use-editor-shortcuts.js +1 -1
- package/dist/es/editor/validation-summary.js +1 -1
- package/dist/es/engine/assert-never.js +1 -1
- package/dist/es/engine/conversion/index.js +1 -1
- package/dist/es/engine/data-source-params.js +17 -17
- package/dist/es/engine/ids.js +1 -1
- package/dist/es/engine/keys.js +6 -3
- package/dist/es/engine/linkage/cycle.js +1 -1
- package/dist/es/engine/linkage/default-evaluator.js +1 -1
- package/dist/es/engine/linkage/effects.js +38 -32
- package/dist/es/engine/linkage/evaluator.js +67 -57
- package/dist/es/engine/linkage/index.js +1 -1
- package/dist/es/engine/linkage/operators.js +2 -2
- package/dist/es/engine/linkage/shape.js +21 -0
- package/dist/es/engine/linkage/source-tracking.js +20 -11
- package/dist/es/engine/linkage/taxonomy.js +1 -1
- package/dist/es/engine/linkage/validator.js +175 -174
- package/dist/es/engine/registry/defaults-mobile.js +1 -1
- package/dist/es/engine/registry/defaults.js +1 -1
- package/dist/es/engine/registry/form-field-registry.js +1 -1
- package/dist/es/engine/schema/column-type.js +6 -2
- package/dist/es/engine/schema/edit-ops.js +1 -1
- package/dist/es/engine/schema/mutate.js +1 -1
- package/dist/es/engine/schema/nodes.js +1 -1
- package/dist/es/engine/schema/permission-bridge.js +4 -3
- package/dist/es/engine/schema/presentation.js +1 -1
- package/dist/es/engine/schema/reconcile.js +1 -1
- package/dist/es/engine/schema/removal-impact.js +60 -39
- package/dist/es/engine/schema/rewrite.js +1 -1
- package/dist/es/engine/schema/validate.js +1 -1
- package/dist/es/engine/schema/walk.js +1 -1
- package/dist/es/engine/validation.js +1 -1
- package/dist/es/icons.js +1 -1
- package/dist/es/index.js +6 -6
- package/dist/es/render/chrome/mobile-chrome.js +67 -66
- package/dist/es/render/chrome/pc-chrome.js +38 -37
- package/dist/es/render/chrome/subform-shell.js +1 -1
- package/dist/es/render/data-source-context.js +0 -0
- package/dist/es/render/data-source-param-scope.js +19 -20
- package/dist/es/render/flex-style.js +1 -1
- package/dist/es/render/form-field.js +1 -1
- package/dist/es/render/form-renderer.js +261 -256
- package/dist/es/render/grid-style.js +1 -1
- package/dist/es/render/parts/field-shell.js +29 -22
- package/dist/es/render/parts/label.js +12 -10
- package/dist/es/render/parts/option-order.js +8 -0
- package/dist/es/render/parts/options-status.js +1 -1
- package/dist/es/render/stack-style.js +1 -1
- package/dist/es/render/subform-columns.js +49 -48
- package/dist/es/render/submit.js +73 -53
- package/dist/es/runtime/effects.js +68 -53
- package/dist/es/runtime/field-write.js +15 -5
- package/dist/es/runtime/resolve-scope-values.js +1 -1
- package/dist/es/runtime/runtime-context.js +1 -1
- package/dist/es/runtime/runtime-state-controller.js +91 -78
- package/dist/es/runtime/stabilize-state-map.js +1 -1
- package/dist/es/store/engine-provider.js +1 -1
- package/dist/es/store/form-store.js +147 -111
- package/dist/es/types/chrome.js +1 -1
- package/dist/es/types/component.js +1 -1
- package/dist/es/types/data-source.js +1 -1
- package/dist/es/types/dynamic-value.js +1 -1
- package/dist/es/types/index.js +1 -1
- package/dist/es/types/linkage.js +1 -1
- package/dist/es/types/properties.js +1 -1
- package/dist/es/types/schema.js +1 -1
- package/dist/types/components/mobile/date-adapters.d.ts +21 -0
- package/dist/types/components/mobile/switch.d.ts +5 -3
- package/dist/types/editor/properties/entries/linkage/options.d.ts +16 -0
- package/dist/types/editor/remove-node-confirm.d.ts +6 -0
- package/dist/types/engine/keys.d.ts +5 -0
- package/dist/types/engine/linkage/effects.d.ts +13 -3
- package/dist/types/engine/linkage/shape.d.ts +54 -0
- package/dist/types/engine/linkage/source-tracking.d.ts +20 -1
- package/dist/types/engine/schema/removal-impact.d.ts +23 -0
- package/dist/types/render/data-source-param-scope.d.ts +18 -8
- package/dist/types/render/parts/field-shell.d.ts +16 -1
- package/dist/types/render/parts/label.d.ts +14 -1
- package/dist/types/render/parts/option-order.d.ts +20 -0
- package/dist/types/render/submit.d.ts +7 -4
- package/dist/types/runtime/effects.d.ts +1 -0
- package/dist/types/runtime/field-write.d.ts +7 -1
- package/dist/types/runtime/runtime-state-controller.d.ts +4 -2
- package/dist/types/store/form-store.d.ts +15 -3
- package/dist/types/types/chrome.d.ts +7 -0
- package/dist/types/types/schema.d.ts +19 -5
- package/package.json +5 -5
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
/*! @vef-framework-react/form-editor v2.
|
|
1
|
+
/*! @vef-framework-react/form-editor v2.21.0 made by Venus | 2026-09-14T13:39:26.088Z */
|
|
2
2
|
//#region src/types/data-source.ts
|
|
3
3
|
var e = { resolve: () => Promise.resolve([]) };
|
|
4
4
|
//#endregion
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
/*! @vef-framework-react/form-editor v2.
|
|
1
|
+
/*! @vef-framework-react/form-editor v2.21.0 made by Venus | 2026-09-14T13:39:26.088Z */
|
|
2
2
|
//#region src/types/dynamic-value.ts
|
|
3
3
|
function e(e) {
|
|
4
4
|
if (typeof e != "object" || !e) return !1;
|
package/dist/es/types/index.js
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
/*! @vef-framework-react/form-editor v2.
|
|
1
|
+
/*! @vef-framework-react/form-editor v2.21.0 made by Venus | 2026-09-14T13:39:26.088Z */
|
|
2
2
|
import { defineContainerDefinition as e, defineFieldDefinition as t } from "./component.js";
|
|
3
3
|
import { noopDataSourceResolver as n } from "./data-source.js";
|
|
4
4
|
import { isDynamicValue as r } from "./dynamic-value.js";
|
package/dist/es/types/linkage.js
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
/*! @vef-framework-react/form-editor v2.
|
|
1
|
+
/*! @vef-framework-react/form-editor v2.21.0 made by Venus | 2026-09-14T13:39:26.088Z */
|
package/dist/es/types/schema.js
CHANGED
|
@@ -26,3 +26,24 @@ export declare function fromPickerDate(date: Date, format: string): string;
|
|
|
26
26
|
* canonical format for display.
|
|
27
27
|
*/
|
|
28
28
|
export declare function formatTrigger(value: string, format: string): string;
|
|
29
|
+
/**
|
|
30
|
+
* The selectable range for the mobile date / datetime pickers.
|
|
31
|
+
*
|
|
32
|
+
* antd-mobile's `DatePicker` defaults to `thisYear ± 10` and **clamps the
|
|
33
|
+
* seeded value into that window before rendering the wheel**
|
|
34
|
+
* (`date-picker.js`'s `pickerValue` calls `bound(...)`). So a stored birth date
|
|
35
|
+
* of 1980 opens the picker on today, and confirming without touching anything
|
|
36
|
+
* writes today back — the trigger meanwhile still shows 1980, because it
|
|
37
|
+
* formats the value directly and never goes through the picker. Dates outside
|
|
38
|
+
* the window are also simply unenterable.
|
|
39
|
+
*
|
|
40
|
+
* The PC `DatePicker` imposes no range, and the value is shared across both
|
|
41
|
+
* presentations, so the mobile pickers must not be narrower. These bounds are
|
|
42
|
+
* therefore wide enough to be a non-constraint for form data while staying
|
|
43
|
+
* inside the years the picker's column generator can enumerate.
|
|
44
|
+
*
|
|
45
|
+
* Not applicable to the daterange field: it renders a `CalendarPicker`, whose
|
|
46
|
+
* defaults carry no bounds.
|
|
47
|
+
*/
|
|
48
|
+
export declare const PICKER_MIN_DATE: Date;
|
|
49
|
+
export declare const PICKER_MAX_DATE: Date;
|
|
@@ -8,8 +8,10 @@ import { FieldComponentProps, SwitchField } from '../../types';
|
|
|
8
8
|
* built for text-style controls) on either device.
|
|
9
9
|
*
|
|
10
10
|
* antd-mobile's `Switch` renders a `role="switch"` element with no labelable
|
|
11
|
-
* `id`, so the inline label is presentational
|
|
12
|
-
*
|
|
13
|
-
*
|
|
11
|
+
* `id`, so `<label for>` cannot reach it and the inline label is presentational.
|
|
12
|
+
* The control is therefore named directly with `aria-label` (antd-mobile's
|
|
13
|
+
* `NativeProps` forwards `AriaAttributes`) — `aria-checked` alone is a STATE,
|
|
14
|
+
* and without a name a reader announces every switch on the form identically.
|
|
15
|
+
* `onChange(checked)` maps directly onto the field's boolean value.
|
|
14
16
|
*/
|
|
15
17
|
export declare const MobileSwitch: FC<FieldComponentProps<SwitchField, boolean>>;
|
|
@@ -69,4 +69,20 @@ export declare function getSourceFieldOptions(args: {
|
|
|
69
69
|
* named data sources by id. An unnamed source falls back to its id as the label.
|
|
70
70
|
*/
|
|
71
71
|
export declare function getDataSourceOptions(dataSources: FormDataSource[] | undefined): SourceFieldOption[];
|
|
72
|
+
/**
|
|
73
|
+
* The source key a newly seeded condition should prefer: any option OTHER than
|
|
74
|
+
* the rule's own field, or `undefined` when self is all there is. A
|
|
75
|
+
* self-referencing condition ("show me when my own value is …") is almost
|
|
76
|
+
* always a mistake, so the three places that seed one — creating a rule,
|
|
77
|
+
* switching an expression back to visual mode, and switching a trigger back to
|
|
78
|
+
* 满足条件 — must agree on that much.
|
|
79
|
+
*
|
|
80
|
+
* They deliberately differ on the no-sibling case, so the fallback stays with
|
|
81
|
+
* the caller: creating a rule yields an edge rule instead of a pre-filled
|
|
82
|
+
* self-condition, while the two switches fall back to self rather than refusing
|
|
83
|
+
* an action the user explicitly asked for.
|
|
84
|
+
*/
|
|
85
|
+
export declare function seedSourceKey(options: ReadonlyArray<{
|
|
86
|
+
value: string;
|
|
87
|
+
}>, selfKey: string | undefined): string | undefined;
|
|
72
88
|
export {};
|
|
@@ -6,3 +6,9 @@ import { FormEditorStoreApi } from '../store/form-store';
|
|
|
6
6
|
* committing. A removal with no outside impact stays a single click.
|
|
7
7
|
*/
|
|
8
8
|
export declare function removeNodeWithConfirm(storeApi: FormEditorStoreApi, nodeId: string): void;
|
|
9
|
+
/**
|
|
10
|
+
* Remove one tab through the same impact-aware confirmation. A tab body is a
|
|
11
|
+
* whole subtree of fields, so deleting one must not be quieter than deleting
|
|
12
|
+
* the container that holds it.
|
|
13
|
+
*/
|
|
14
|
+
export declare function removeTabWithConfirm(storeApi: FormEditorStoreApi, tabsId: string, tabId: string): void;
|
|
@@ -78,3 +78,8 @@ export interface ScopeKeyBucket {
|
|
|
78
78
|
* simulation that previews that prune).
|
|
79
79
|
*/
|
|
80
80
|
export declare function collectSubtreeKeysByScope(node: Block, baseScope: ScopePath): ScopeKeyBucket[];
|
|
81
|
+
/**
|
|
82
|
+
* {@link collectSubtreeKeysByScope} over a block LIST rather than a single
|
|
83
|
+
* subtree root — what a tab body is, since a tab is not itself a `Block`.
|
|
84
|
+
*/
|
|
85
|
+
export declare function collectBlocksKeysByScope(blocks: Block[], baseScope: ScopePath): ScopeKeyBucket[];
|
|
@@ -26,11 +26,21 @@ export interface ConditionEffectRule {
|
|
|
26
26
|
ruleId: string;
|
|
27
27
|
condition: LinkageCondition;
|
|
28
28
|
/**
|
|
29
|
-
* The
|
|
30
|
-
*
|
|
31
|
-
*
|
|
29
|
+
* The FORM-VALUE fields this condition reads. The `"always"` tracker diffs
|
|
30
|
+
* these between evaluations so an unrelated field change does not re-fire
|
|
31
|
+
* {@link alwaysActions}. Empty is a real answer — a condition on a `$`-rooted
|
|
32
|
+
* context path depends on nothing in the form — and must not be confused with
|
|
33
|
+
* {@link opaque}.
|
|
32
34
|
*/
|
|
33
35
|
sourceKeys: string[];
|
|
36
|
+
/**
|
|
37
|
+
* Whether the condition reads inputs that cannot be enumerated (an
|
|
38
|
+
* `expression` condition). Only then does the tracker fall back to diffing
|
|
39
|
+
* the whole values object; treating an empty {@link sourceKeys} as opaque
|
|
40
|
+
* turned a context-only condition's `"always"` actions into one dispatch per
|
|
41
|
+
* keystroke anywhere on the form.
|
|
42
|
+
*/
|
|
43
|
+
opaque: boolean;
|
|
34
44
|
/**
|
|
35
45
|
* The rule's effect actions, in declaration order — every one fires on the
|
|
36
46
|
* condition's false→true rising edge. State actions (if any) are excluded;
|
|
@@ -0,0 +1,54 @@
|
|
|
1
|
+
import { FieldLinkage, FieldLinkageAction, FieldLinkageRule, LinkageCondition, LinkageTriggerKind } from '../../types';
|
|
2
|
+
/**
|
|
3
|
+
* Structural trust guards for host-supplied linkage.
|
|
4
|
+
*
|
|
5
|
+
* `FormRenderer` never calls `validateSchema` — the runtime schema is whatever
|
|
6
|
+
* the host handed it, typically JSON parsed from storage. So every render-path
|
|
7
|
+
* reader must treat a rule as unknown data and degrade to "skipped" rather than
|
|
8
|
+
* throw: a malformed rule inside a nested container would otherwise take the
|
|
9
|
+
* whole form down to a white screen, with a `TypeError` naming a React internal
|
|
10
|
+
* rather than the offending schema.
|
|
11
|
+
*
|
|
12
|
+
* The validator lane has its own inline guards because it reports each fault as
|
|
13
|
+
* an issue; these are the silent counterpart for the lane that has no reporting
|
|
14
|
+
* channel. Keeping them here means a reader adds a call rather than an ad-hoc
|
|
15
|
+
* `?.`, which is how the guards drifted apart in the first place.
|
|
16
|
+
*/
|
|
17
|
+
/**
|
|
18
|
+
* A linkage block's rules, or an empty list when the block is absent or its
|
|
19
|
+
* `rules` is not an array. A non-array `rules` (`{}` from a hand-edited or
|
|
20
|
+
* half-migrated document) is the case a bare `?? []` misses: it is neither null
|
|
21
|
+
* nor undefined, so it reaches `for…of` and throws "is not iterable".
|
|
22
|
+
*/
|
|
23
|
+
export declare function linkageRules(linkage: FieldLinkage | undefined): FieldLinkageRule[];
|
|
24
|
+
/**
|
|
25
|
+
* A rule's trigger kind, or `undefined` when the rule or its trigger is not a
|
|
26
|
+
* record. Callers compare against the kind they want, so an unusable rule
|
|
27
|
+
* simply never matches.
|
|
28
|
+
*/
|
|
29
|
+
export declare function ruleTriggerKind(rule: FieldLinkageRule): LinkageTriggerKind | undefined;
|
|
30
|
+
/**
|
|
31
|
+
* The condition of a `condition`-triggered rule, or `undefined` for any other
|
|
32
|
+
* trigger kind and for a malformed rule. Callers that need both the kind check
|
|
33
|
+
* and the payload use this alone: reading `rule.trigger.condition` back off the
|
|
34
|
+
* rule after a {@link ruleTriggerKind} check re-enters the unguarded union and
|
|
35
|
+
* loses the narrowing.
|
|
36
|
+
*/
|
|
37
|
+
export declare function ruleCondition(rule: FieldLinkageRule): LinkageCondition | undefined;
|
|
38
|
+
/**
|
|
39
|
+
* A rule's actions, or an empty list when the rule is malformed. Pairs with
|
|
40
|
+
* {@link ruleTriggerKind}: a reader that filters by trigger still has to reach
|
|
41
|
+
* into `actions`, and both halves must survive the same broken rule.
|
|
42
|
+
*/
|
|
43
|
+
export declare function ruleActions(rule: FieldLinkageRule): FieldLinkageAction[];
|
|
44
|
+
/**
|
|
45
|
+
* Whether any rule can ever lift a `defaults.hidden` block into view.
|
|
46
|
+
*
|
|
47
|
+
* Only a condition-triggered `show` counts: a `show` on an edge trigger is
|
|
48
|
+
* separately rejected (`state_action_on_edge_trigger`) and never reaches the
|
|
49
|
+
* state lane, so it must not be mistaken for a way out. Shared by the linkage
|
|
50
|
+
* validator and the editor's removal-impact preview — the two describe the same
|
|
51
|
+
* property to the user (one as a publish-time warning, one as a delete
|
|
52
|
+
* confirmation), so they cannot be allowed to disagree.
|
|
53
|
+
*/
|
|
54
|
+
export declare function hasConditionTriggeredShow(rules: unknown): boolean;
|
|
@@ -21,5 +21,24 @@ interface LinkageBearer {
|
|
|
21
21
|
* re-evaluate on any value change.
|
|
22
22
|
*/
|
|
23
23
|
export declare function getLinkageSourceKeys(node: LinkageBearer): string[];
|
|
24
|
-
|
|
24
|
+
/**
|
|
25
|
+
* A condition's form-value dependencies, plus whether any part of it is opaque
|
|
26
|
+
* — i.e. reads inputs that cannot be enumerated statically.
|
|
27
|
+
*
|
|
28
|
+
* Only an `expression` condition is opaque. A `$`-rooted leaf
|
|
29
|
+
* (`$user.departmentId`) has a perfectly knowable dependency; it just is not a
|
|
30
|
+
* form value, so it contributes no key while leaving the condition
|
|
31
|
+
* enumerable. Collapsing the two into "empty key set" is what let a context
|
|
32
|
+
* condition be treated as opaque, which the `always` retrigger reads as
|
|
33
|
+
* "re-fire on any value change".
|
|
34
|
+
*/
|
|
35
|
+
export declare function describeConditionSources(condition: LinkageCondition): {
|
|
36
|
+
keys: string[];
|
|
37
|
+
opaque: boolean;
|
|
38
|
+
};
|
|
39
|
+
/**
|
|
40
|
+
* Collect a condition's form-value source keys into `out`, returning whether
|
|
41
|
+
* any visited node was opaque (see {@link describeConditionSources}).
|
|
42
|
+
*/
|
|
43
|
+
export declare function collectConditionSourceKeys(condition: LinkageCondition, out: Set<string>): boolean;
|
|
25
44
|
export {};
|
|
@@ -1,4 +1,5 @@
|
|
|
1
1
|
import { FieldLinkage, PresentationLayer } from '../../types';
|
|
2
|
+
import { ScopeKeyBucket } from '../keys';
|
|
2
3
|
export interface RemovalImpactOwner {
|
|
3
4
|
ownerId: string;
|
|
4
5
|
ownerLabel: string;
|
|
@@ -37,3 +38,25 @@ export declare function hasRemovalImpact(impact: RemovalImpact): boolean;
|
|
|
37
38
|
* removal happens on the presentation it resolves against (the pc layer).
|
|
38
39
|
*/
|
|
39
40
|
export declare function collectRemovalImpact(layer: PresentationLayer, nodeId: string, formLinkage?: FieldLinkage): RemovalImpact;
|
|
41
|
+
/**
|
|
42
|
+
* What deleting one TAB of a tabs container does to the rest of the schema.
|
|
43
|
+
*
|
|
44
|
+
* A tab carries a whole body of fields, so removing one is as destructive as
|
|
45
|
+
* removing a container — but it is not a node removal, and routing it through a
|
|
46
|
+
* plain block update would skip the reference prune entirely: surviving rules
|
|
47
|
+
* would keep pointing at keys that no longer exist, and the freed key would
|
|
48
|
+
* later be handed to an unrelated new field, silently rebinding those rules to
|
|
49
|
+
* it. Tabs never open a value scope, so the body's keys live in the tabs node's
|
|
50
|
+
* own scope.
|
|
51
|
+
*/
|
|
52
|
+
export declare function collectTabRemovalImpact(layer: PresentationLayer, tabsId: string, tabId: string, formLinkage?: FieldLinkage): RemovalImpact;
|
|
53
|
+
/**
|
|
54
|
+
* Drop one tab from a tabs container, returning the resulting layer and the
|
|
55
|
+
* keys that died with the body — `undefined` when the tab (or its container)
|
|
56
|
+
* does not resolve, or when it is the last tab (a tabs container always keeps
|
|
57
|
+
* at least one).
|
|
58
|
+
*/
|
|
59
|
+
export declare function removeTabBody(layer: PresentationLayer, tabsId: string, tabId: string): {
|
|
60
|
+
layer: PresentationLayer;
|
|
61
|
+
buckets: ScopeKeyBucket[];
|
|
62
|
+
} | undefined;
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
import { ReactElement, ReactNode } from 'react';
|
|
2
2
|
import { ParamEvaluator } from '../engine/data-source-params';
|
|
3
|
-
import {
|
|
3
|
+
import { RuntimeFormValues } from '../runtime/types';
|
|
4
4
|
import { EvaluationContext, LinkageEvaluators } from '../types';
|
|
5
5
|
/**
|
|
6
6
|
* What a bound data-source parameter is evaluated against: the live form values
|
|
@@ -21,15 +21,25 @@ export interface DataSourceParamScope {
|
|
|
21
21
|
/**
|
|
22
22
|
* Publishes the evaluation scope for bound data-source parameters.
|
|
23
23
|
*
|
|
24
|
-
*
|
|
25
|
-
*
|
|
26
|
-
* parameter
|
|
27
|
-
*
|
|
24
|
+
* Mounted by `LinkageScope`, once per VALUE SCOPE — the root form and every
|
|
25
|
+
* subform row — with that scope's own values. A row must publish its own or a
|
|
26
|
+
* bound parameter inside a repeated row resolves against the whole form, where
|
|
27
|
+
* the row's keys do not exist: the parameter drops out (an unresolved parameter
|
|
28
|
+
* is omitted, not sent empty), every row issues the same unfiltered request,
|
|
29
|
+
* and because the cache is keyed on the resolved request they all collapse onto
|
|
30
|
+
* one shared option list. Per-row cascading becomes structurally impossible
|
|
31
|
+
* rather than merely wrong once. The effect lane already scoped its own
|
|
32
|
+
* `resolveRequest` this way, so the two lanes now answer identically — which is
|
|
33
|
+
* what the contract claims.
|
|
34
|
+
*
|
|
35
|
+
* `values` is `undefined` when the schema binds no parameter at all, which
|
|
36
|
+
* publishes no scope and keeps every select out of the keystroke render path —
|
|
37
|
+
* the same concern that makes the runtime state map reference-stabilized before
|
|
38
|
+
* it reaches fields.
|
|
28
39
|
*/
|
|
29
|
-
export declare function DataSourceParamScopeProvider({ children, context,
|
|
40
|
+
export declare function DataSourceParamScopeProvider({ children, context, evaluators, values }: {
|
|
30
41
|
children: ReactNode;
|
|
31
|
-
|
|
32
|
-
form: RuntimeForm;
|
|
42
|
+
values: RuntimeFormValues | undefined;
|
|
33
43
|
evaluators?: LinkageEvaluators;
|
|
34
44
|
context?: EvaluationContext;
|
|
35
45
|
}): ReactElement;
|
|
@@ -29,5 +29,20 @@ export interface FieldShellProps {
|
|
|
29
29
|
label: ReactNode;
|
|
30
30
|
labelPosition?: LabelPosition;
|
|
31
31
|
required?: boolean;
|
|
32
|
+
/**
|
|
33
|
+
* How the label associates with what it names.
|
|
34
|
+
*
|
|
35
|
+
* `"control"` (the default) emits `<label for={domId}>`, which requires the
|
|
36
|
+
* field to put `domId` on a LABELABLE element — an input, select, textarea or
|
|
37
|
+
* button.
|
|
38
|
+
*
|
|
39
|
+
* `"group"` is for fields that render a set rather than a single control
|
|
40
|
+
* (radio / checkbox groups, the upload dropzone, the code editor): `for` is
|
|
41
|
+
* inert against their wrapper, so the label carries an id and the body
|
|
42
|
+
* becomes a `role="group"` that points back at it. Without this the field has
|
|
43
|
+
* NO accessible name — the reader announces the first option and nothing
|
|
44
|
+
* about the question being asked.
|
|
45
|
+
*/
|
|
46
|
+
labelledBy?: "control" | "group";
|
|
32
47
|
}
|
|
33
|
-
export declare function FieldShell({ children, domId, errors, helperText, label, labelPosition, required }: FieldShellProps): ReactElement;
|
|
48
|
+
export declare function FieldShell({ children, domId, errors, helperText, label, labelPosition, labelledBy, required }: FieldShellProps): ReactElement;
|
|
@@ -1,8 +1,21 @@
|
|
|
1
1
|
import { ReactElement, ReactNode } from 'react';
|
|
2
2
|
import { LabelPosition } from '../../types';
|
|
3
3
|
export interface LabelProps {
|
|
4
|
+
/**
|
|
5
|
+
* Hide the label from assistive technology. For a control that carries the
|
|
6
|
+
* same text as its own `aria-label` (the mobile switch, whose antd-mobile
|
|
7
|
+
* element cannot be reached by `<label for>`), so the name is announced once
|
|
8
|
+
* rather than twice.
|
|
9
|
+
*/
|
|
10
|
+
"aria-hidden"?: boolean;
|
|
4
11
|
children: ReactNode;
|
|
5
12
|
htmlFor?: string;
|
|
13
|
+
/**
|
|
14
|
+
* DOM id, so a `role="group"` body can point back at this label. Used
|
|
15
|
+
* instead of `htmlFor` for fields that render a set rather than one
|
|
16
|
+
* labelable control.
|
|
17
|
+
*/
|
|
18
|
+
id?: string;
|
|
6
19
|
position?: LabelPosition;
|
|
7
20
|
required?: boolean;
|
|
8
21
|
/**
|
|
@@ -17,4 +30,4 @@ export interface LabelProps {
|
|
|
17
30
|
* `position` only affects its own spacing; the surrounding {@link FieldShell}
|
|
18
31
|
* owns the label-vs-control axis.
|
|
19
32
|
*/
|
|
20
|
-
export declare function Label({ children, htmlFor, position, required, title }: LabelProps): ReactElement;
|
|
33
|
+
export declare function Label({ "aria-hidden": ariaHidden, children, htmlFor, id, position, required, title }: LabelProps): ReactElement;
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
import { FieldOption } from '../../types';
|
|
2
|
+
/**
|
|
3
|
+
* Normalize a multi-select value to the option list's own order, keeping only
|
|
4
|
+
* values the list still offers.
|
|
5
|
+
*
|
|
6
|
+
* The order has to be a property of the SCHEMA, not of the widget or of the
|
|
7
|
+
* order the user happened to click in: antd's `Checkbox.Group` sorts its
|
|
8
|
+
* emitted array by option index, while antd-mobile's appends each check in
|
|
9
|
+
* click order. Left alone, the same two clicks produce `["read", "music"]` on
|
|
10
|
+
* desktop and `["music", "read"]` on a phone — two different rows in
|
|
11
|
+
* `form_data` for one user intent, and a spurious diff whenever someone
|
|
12
|
+
* resubmits from the other device.
|
|
13
|
+
*
|
|
14
|
+
* Filtering to the registered values matters for the same reason on the way
|
|
15
|
+
* out: the backend validates a selection against the field's enumerated
|
|
16
|
+
* options and rejects anything else, so a value left over from an option the
|
|
17
|
+
* designer has since removed makes the whole submission fail. antd already
|
|
18
|
+
* drops those; this is what makes the mobile renderer agree.
|
|
19
|
+
*/
|
|
20
|
+
export declare function orderByOptions(value: readonly unknown[], options: readonly FieldOption[]): Array<string | number>;
|
|
@@ -92,11 +92,14 @@ export declare function validateRuntimeField(args: {
|
|
|
92
92
|
*/
|
|
93
93
|
export declare function validateKeyedFieldValue(field: KeyedFormField, required: boolean, value: unknown): string | undefined;
|
|
94
94
|
/**
|
|
95
|
-
* Whether a keyed field is currently required
|
|
96
|
-
*
|
|
97
|
-
*
|
|
95
|
+
* Whether a keyed field is currently required. The runtime state is the whole
|
|
96
|
+
* answer: `evaluateLinkageResolved` seeds the fold with the field's static
|
|
97
|
+
* `validate.required` and the permission clamp trims it, so a fired `optional`
|
|
98
|
+
* relaxes a statically-required field and a non-writable clamp zeroes it.
|
|
99
|
+
* Re-reading `validate.required` here would put the static flag back on top of
|
|
100
|
+
* both.
|
|
98
101
|
*/
|
|
99
|
-
export declare function isRuntimeRequired(
|
|
102
|
+
export declare function isRuntimeRequired(_field: KeyedFormField, runtimeState: RuntimeFieldState): boolean;
|
|
100
103
|
/**
|
|
101
104
|
* Static constraint rules (`minLength` / `maxLength` / `min` / `max` / `pattern`)
|
|
102
105
|
* checked against a present value. `validate.message`, when set, overrides the
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
import { FieldPermission } from '../types';
|
|
1
|
+
import { FieldPermission, KeyedFormField } from '../types';
|
|
2
2
|
import { RuntimeForm } from './types';
|
|
3
3
|
/**
|
|
4
4
|
* The single gate for every programmatic form-value write: the state lane's
|
|
@@ -33,5 +33,11 @@ export declare function writeFieldValue(args: {
|
|
|
33
33
|
* The scope's field-name prefix: `""` at the root, `"lines[0]."` in a row.
|
|
34
34
|
*/
|
|
35
35
|
prefix: string;
|
|
36
|
+
/**
|
|
37
|
+
* The field being written, when the caller knows it. Used only to coerce the
|
|
38
|
+
* value to the shape that field's control and validation expect; omitted for
|
|
39
|
+
* a `set_field` aiming at a key the scope's schema does not declare.
|
|
40
|
+
*/
|
|
41
|
+
targetField?: KeyedFormField;
|
|
36
42
|
value: unknown;
|
|
37
43
|
}): void;
|
|
@@ -7,7 +7,8 @@ import { RuntimeForm } from './types';
|
|
|
7
7
|
* form-values object. `form.store.state.values` is one shared reference per
|
|
8
8
|
* write, so the default `Object.is` compare on the selector is correct here.
|
|
9
9
|
*/
|
|
10
|
-
export declare function RuntimeStateController({ children, evaluators, evaluationContext, fieldPermissions, form, schema, sinks }: {
|
|
10
|
+
export declare function RuntimeStateController({ boundParams, children, evaluators, evaluationContext, fieldPermissions, form, schema, sinks }: {
|
|
11
|
+
boundParams: boolean;
|
|
11
12
|
children: ReactNode;
|
|
12
13
|
evaluators: LinkageEvaluators | undefined;
|
|
13
14
|
evaluationContext: EvaluationContext | undefined;
|
|
@@ -23,7 +24,8 @@ export declare function RuntimeStateController({ children, evaluators, evaluatio
|
|
|
23
24
|
* elsewhere. Installs a NESTED selector-context Provider so the template field
|
|
24
25
|
* ids (which repeat across rows) resolve to this row's own state map.
|
|
25
26
|
*/
|
|
26
|
-
export declare function SubformRowController({ children, evaluators, evaluationContext, form, prefix, sinks, templateSchema }: {
|
|
27
|
+
export declare function SubformRowController({ boundParams, children, evaluators, evaluationContext, form, prefix, sinks, templateSchema }: {
|
|
28
|
+
boundParams: boolean;
|
|
27
29
|
children: ReactNode;
|
|
28
30
|
evaluators: LinkageEvaluators | undefined;
|
|
29
31
|
evaluationContext: EvaluationContext | undefined;
|
|
@@ -137,6 +137,16 @@ export interface FormEditorStoreState {
|
|
|
137
137
|
* form-level linkage when root-scope pc keys are affected.
|
|
138
138
|
*/
|
|
139
139
|
removeNode: (nodeId: string) => void;
|
|
140
|
+
/**
|
|
141
|
+
* Remove one tab of a tabs container, together with its whole body. Runs the
|
|
142
|
+
* same reference prune and selection cleanup as {@link removeNode} — a tab
|
|
143
|
+
* body is a subtree, and dropping it through a plain block update left every
|
|
144
|
+
* surviving rule pointing at keys that no longer existed, then silently
|
|
145
|
+
* rebound those rules when the freed key was handed to a new field. A tabs
|
|
146
|
+
* container always keeps at least one tab, so removing the last one is a
|
|
147
|
+
* no-op.
|
|
148
|
+
*/
|
|
149
|
+
removeTab: (tabsId: string, tabId: string) => void;
|
|
140
150
|
/**
|
|
141
151
|
* Deep-clone a node (fresh ids, fresh keys) and drop it on a new row right
|
|
142
152
|
* below its source.
|
|
@@ -241,11 +251,13 @@ export declare const useFormEditorStore: UseStore<FormEditorStoreState>;
|
|
|
241
251
|
* device resolves to the shared empty layer, so the value identity is stable.
|
|
242
252
|
*/
|
|
243
253
|
export declare function useCurrentLayer(): PresentationLayer;
|
|
254
|
+
export declare function selectFieldCount(state: FormEditorStoreState): number;
|
|
244
255
|
/**
|
|
245
|
-
*
|
|
246
|
-
*
|
|
256
|
+
* Fields across BOTH presentations. What a whole-schema action (clearing,
|
|
257
|
+
* importing) actually affects — `selectFieldCount` speaks for the device on
|
|
258
|
+
* screen, which understates a form whose other device carries the design.
|
|
247
259
|
*/
|
|
248
|
-
export declare function
|
|
260
|
+
export declare function selectTotalFieldCount(state: FormEditorStoreState): number;
|
|
249
261
|
/**
|
|
250
262
|
* Total linkage rule count the designer has authored: field-level rules across
|
|
251
263
|
* the active device's presentation PLUS the form-level event rules. The footer
|
|
@@ -21,6 +21,13 @@ export interface TabsChromeProps {
|
|
|
21
21
|
}
|
|
22
22
|
export interface SubformChromeProps {
|
|
23
23
|
title?: ReactNode;
|
|
24
|
+
/**
|
|
25
|
+
* The subform field's own validation errors — "at least one row" on a
|
|
26
|
+
* required subform, and a table variant's rolled-up row error. Rendered
|
|
27
|
+
* under the body; without a slot here they reach the user nowhere, since a
|
|
28
|
+
* subform mounts one field for the whole array.
|
|
29
|
+
*/
|
|
30
|
+
errors?: string[];
|
|
24
31
|
children: ReactNode;
|
|
25
32
|
}
|
|
26
33
|
export interface SubformRowChromeProps {
|
|
@@ -433,7 +433,10 @@ export interface RadioField extends FormFieldBase, KeyedNode, Validatable {
|
|
|
433
433
|
buttonStyle?: "outline" | "solid";
|
|
434
434
|
/**
|
|
435
435
|
* Option layout direction. Maps to antd `Radio.Group` `orientation` on PC and
|
|
436
|
-
* drives the flex direction on mobile. Defaults to vertical
|
|
436
|
+
* drives the flex direction on mobile. Defaults to vertical — applied
|
|
437
|
+
* EXPLICITLY by both renderers, since antd's own default is horizontal and
|
|
438
|
+
* antd-mobile's is vertical, which laid the same schema out differently on
|
|
439
|
+
* the two devices.
|
|
437
440
|
*/
|
|
438
441
|
direction?: "horizontal" | "vertical";
|
|
439
442
|
}
|
|
@@ -445,7 +448,9 @@ export interface CheckboxGroupField extends FormFieldBase, KeyedNode, Validatabl
|
|
|
445
448
|
helperText?: string;
|
|
446
449
|
dataSource?: FieldOptionSource;
|
|
447
450
|
/**
|
|
448
|
-
* Option layout direction.
|
|
451
|
+
* Option layout direction. Defaults to vertical, applied explicitly by both
|
|
452
|
+
* renderers (see RadioField.direction). antd `Checkbox.Group` has no
|
|
453
|
+
* orientation prop, so
|
|
449
454
|
* the PC renderer realizes vertical layout via flex; the mobile renderer drives
|
|
450
455
|
* its flex direction the same way. Defaults to vertical.
|
|
451
456
|
*/
|
|
@@ -846,9 +851,18 @@ export type Block = FormField | ContainerNode;
|
|
|
846
851
|
*/
|
|
847
852
|
export type KeyedNodeUnion = Extract<Block, KeyedNode>;
|
|
848
853
|
/**
|
|
849
|
-
* Which device a {@link PresentationLayer} targets.
|
|
850
|
-
*
|
|
851
|
-
*
|
|
854
|
+
* Which device a {@link PresentationLayer} targets.
|
|
855
|
+
*
|
|
856
|
+
* PC and mobile each carry an independent field tree and layout, and the two
|
|
857
|
+
* designs may legitimately differ: a field can exist on one device and not the
|
|
858
|
+
* other, and the same field can sit in a different container or order.
|
|
859
|
+
*
|
|
860
|
+
* The DATA layer is shared, though — variables, data sources, and keys. A key
|
|
861
|
+
* names one value on both devices, which is what `walkUniqueRootKeyedFields`
|
|
862
|
+
* relies on when it folds the two trees into one field inventory deduped by
|
|
863
|
+
* key. So renaming a field that both devices carry renames it on both
|
|
864
|
+
* (`setFieldKey`); letting the two drift apart would project one field as two
|
|
865
|
+
* and hand the backend a phantom.
|
|
852
866
|
*/
|
|
853
867
|
export type PresentationDevice = "pc" | "mobile";
|
|
854
868
|
/**
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@vef-framework-react/form-editor",
|
|
3
|
-
"version": "2.
|
|
3
|
+
"version": "2.21.0",
|
|
4
4
|
"private": false,
|
|
5
5
|
"description": "Form editor for VEF framework",
|
|
6
6
|
"keywords": [
|
|
@@ -46,10 +46,10 @@
|
|
|
46
46
|
"@emotion/react": "^11.14.0",
|
|
47
47
|
"antd-mobile": "^5.42.3",
|
|
48
48
|
"lucide-react": "^1.23.0",
|
|
49
|
-
"@vef-framework-react/
|
|
50
|
-
"@vef-framework-react/
|
|
51
|
-
"@vef-framework-react/
|
|
52
|
-
"@vef-framework-react/
|
|
49
|
+
"@vef-framework-react/components": "2.21.0",
|
|
50
|
+
"@vef-framework-react/core": "2.21.0",
|
|
51
|
+
"@vef-framework-react/hooks": "2.21.0",
|
|
52
|
+
"@vef-framework-react/shared": "2.21.0"
|
|
53
53
|
},
|
|
54
54
|
"devDependencies": {
|
|
55
55
|
"react": "^19.2.7"
|