@formily-design/formily-antd 1.0.20 → 1.0.21

package/esm/components/DatePicker/preview.js

@@ -1,8 +1,46 @@
 import { DatePicker as FormilyDatePicker } from '@formily/antd-v5';
 import { createBehavior, createResource } from '@formily-design/core';
-import { createFieldSchema } from '../Field';
+import { VALUE_MAPPING_SCHEMA_KEY } from '@formily-design/core';
+import { createFieldSchema } from '../Field/shared';
+import { createValueMappingSettingsReaction } from '../Field/valueMapping';
 import { AllSchemas } from '../../schemas';
 import { AllLocales } from '../../locales';
+const valueMappingTargetPaths = [
+    `${VALUE_MAPPING_SCHEMA_KEY}.targets.0.path`,
+    `${VALUE_MAPPING_SCHEMA_KEY}.targets.1.path`,
+];
+const createMappingPathSchema = (titleToken) => ({
+    type: 'string',
+    title: `{{$node.getMessage("settings.value-mapping-group.${titleToken}")}}`,
+    'x-decorator': 'FormItem',
+    'x-decorator-props': {
+        // SettingsForm 默认不展示 feedback；映射路径需要即时呈现输入校验结果。
+        feedbackLayout: 'loose',
+    },
+    'x-component': 'Input',
+    'x-component-props': {
+        allowClear: true,
+    },
+});
+const ValueMappingGroup = {
+    type: 'void',
+    'x-component': 'CollapseItem',
+    'x-component-props': { defaultExpand: false },
+    // 分组只挂一个 reaction，避免协议同步与反馈校验的两个 autorun 产生竞态。
+    'x-reactions': [
+        createValueMappingSettingsReaction({
+            adapter: 'tuple',
+            targetPaths: valueMappingTargetPaths,
+            scope: 'relative',
+            submitSource: false,
+            getMessage: (error, scope) => { var _a; return (_a = scope.$node) === null || _a === void 0 ? void 0 : _a.getMessage(`settings.value-mapping-group.${error}`); },
+        }),
+    ],
+    properties: {
+        [valueMappingTargetPaths[0]]: createMappingPathSchema('startPath'),
+        [valueMappingTargetPaths[1]]: createMappingPathSchema('endPath'),
+    },
+};
 export const DatePicker = FormilyDatePicker;
 DatePicker.Behavior = createBehavior({
     name: 'DatePicker',
@@ -17,7 +55,9 @@ DatePicker.Behavior = createBehavior({
     extends: ['Field'],
     selector: (node) => node.props['x-component'] === 'DatePicker.RangePicker',
     designerProps: {
-        propsSchema: createFieldSchema(AllSchemas.DatePicker.RangePicker),
+        propsSchema: createFieldSchema(AllSchemas.DatePicker.RangePicker, undefined, {
+            'value-mapping-group': ValueMappingGroup,
+        }),
     },
     designerLocales: AllLocales.DateRangePicker,
 });

package/esm/components/Field/index.d.ts

@@ -1,2 +1,3 @@
 export * from './preview';
 export * from './shared';
+export * from './valueMapping';

package/esm/components/Field/index.js

@@ -1,2 +1,3 @@
 export * from './preview';
 export * from './shared';
+export * from './valueMapping';

package/esm/components/Field/shared.d.ts

@@ -1,4 +1,4 @@
 import { ISchema } from '@formily/json-schema';
 export declare const createComponentSchema: (component: ISchema, decorator: ISchema) => Record<string, ISchema | undefined>;
-export declare const createFieldSchema: (component?: ISchema, decorator?: ISchema) => ISchema;
+export declare const createFieldSchema: (component?: ISchema, decorator?: ISchema, additionalGroups?: Record<string, ISchema>) => ISchema;
 export declare const createVoidFieldSchema: (component?: ISchema, decorator?: ISchema) => ISchema;

package/esm/components/Field/shared.js

@@ -64,10 +64,10 @@ export const createComponentSchema = (component, decorator) => {
         },
     };
 };
-export const createFieldSchema = (component, decorator = AllSchemas.FormItem) => {
+export const createFieldSchema = (component, decorator = AllSchemas.FormItem, additionalGroups = {}) => {
     return {
         type: 'object',
-        properties: Object.assign({ 'field-group': {
+        properties: Object.assign(Object.assign({ 'field-group': {
                 type: 'void',
                 'x-component': 'CollapseItem',
                 properties: {
@@ -170,7 +170,7 @@ export const createFieldSchema = (component, decorator = AllSchemas.FormItem) =>
                         'x-component': 'Switch',
                     },
                 },
-            } }, createComponentSchema(component, decorator)),
+            } }, additionalGroups), createComponentSchema(component, decorator)),
     };
 };
 export const createVoidFieldSchema = (component, decorator = AllSchemas.FormItem) => {

package/esm/components/Field/valueMapping.d.ts

@@ -0,0 +1,45 @@
+import type { IScopeContext, SchemaReaction } from '@formily/json-schema';
+import { VALUE_MAPPING_RELATIVE_SCOPE } from '@formily-design/core';
+import type { ValueMappingTargetValidationError } from '@formily-design/core';
+export type { ValueMappingTargetValidationError } from '@formily-design/core';
+export interface ICreateValueMappingSettingsReactionOptions {
+    /**
+     * 映射运行时使用的 adapter 名称，例如 tuple。
+     */
+    adapter: string;
+    /**
+     * 设置表单中 target path 输入框的完整数据路径。
+     *
+     * 注意：这里配置的是输入框在设置表单中的路径，而不是用户最终填写的
+     * startDate、address.provinceCode 等业务字段路径。
+     */
+    targetPaths: string[];
+    scope?: typeof VALUE_MAPPING_RELATIVE_SCOPE;
+    submitSource?: boolean;
+    /**
+     * 根据校验错误码返回当前语言的提示文案。scope 会透传 Formily
+     * reaction 的作用域，因此设置器可以使用 `$node.getMessage` 读取节点语言。
+     */
+    getMessage: (error: ValueMappingTargetValidationError, scope: IScopeContext) => string | undefined;
+}
+/**
+ * 校验一组手动输入的映射 target 路径。
+ *
+ * 空数组表示尚未启用映射；一旦任意路径有值，所有 target 都必须填写、合法且唯一。
+ * 该方法与具体组件数量无关，日期范围、省市区等配置界面均可复用。
+ */
+export declare const validateValueMappingTargetPaths: (paths: unknown[]) => ValueMappingTargetValidationError | undefined;
+/**
+ * 创建设置表单使用的 value-mapping 协议与校验 reaction。
+ *
+ * 协议和反馈必须由一个 autorun 编排。若分别挂两个 x-reactions，它们对同一
+ * 次 onInput 的调度顺序不稳定：协议 reaction 规范化数字路径时会再次写值，
+ * 校验 reaction 可能拿到中间快照，导致残留错误或覆盖刚写入的配置。本 reaction
+ * 先读取一次 targetValues，再同步反馈和协议，保证二者始终对应同一组输入。
+ *
+ * target 全空时先同步清除反馈，让界面立即恢复；父级协议延迟到当前 onInput/batch
+ * 结束后的 Promise 微任务再删除。微任务执行前会重新读取最新 target：若用户已快速
+ * 重新输入则跳过删除，避免旧 cleanup 误删。按 Form 隔离的 WeakSet 会合并同一 Form
+ * 的重复 cleanup，同时不会影响其它设置 Form。
+ */
+export declare const createValueMappingSettingsReaction: ({ adapter, targetPaths, scope, submitSource, getMessage, }: ICreateValueMappingSettingsReactionOptions) => SchemaReaction;

package/esm/components/Field/valueMapping.js

@@ -0,0 +1,117 @@
+import { untracked } from '@formily/reactive';
+import { VALUE_MAPPING_RELATIVE_SCOPE, VALUE_MAPPING_SCHEMA_KEY, VALUE_MAPPING_VERSION, validateValueMappingTargetPaths as validateSharedTargetPaths, } from '@formily-design/core';
+// 一个 Form 只允许排队一个 cleanup；WeakSet 不持有 Form 强引用，也不会串扰其它 Form。
+const pendingMappingCleanups = new WeakSet();
+const hasInputText = (value) => typeof value === 'string' && Boolean(value.trim());
+/**
+ * 校验一组手动输入的映射 target 路径。
+ *
+ * 空数组表示尚未启用映射；一旦任意路径有值，所有 target 都必须填写、合法且唯一。
+ * 该方法与具体组件数量无关，日期范围、省市区等配置界面均可复用。
+ */
+export const validateValueMappingTargetPaths = (paths) => validateSharedTargetPaths(paths, { allowEmpty: true });
+/** 将同一份 target 快照规范化为运行时协议。 */
+const syncValueMappingProtocol = (form, targetValues, adapter, scope, submitSource) => {
+    const normalizedTargets = targetValues.map((path) => ({
+        path: typeof path === 'string' ? path.trim() : '',
+    }));
+    const currentTargets = form.getValuesIn(`${VALUE_MAPPING_SCHEMA_KEY}.targets`);
+    const targetsChanged = !Array.isArray(currentTargets) ||
+        currentTargets.length !== normalizedTargets.length ||
+        normalizedTargets.some((target, index) => { var _a; return ((_a = currentTargets[index]) === null || _a === void 0 ? void 0 : _a.path) !== target.path; });
+    // FormPath 的数字点路径默认可能生成对象，这里统一规范化为运行时协议要求的数组。
+    if (targetsChanged) {
+        form.setValuesIn(`${VALUE_MAPPING_SCHEMA_KEY}.targets`, normalizedTargets);
+    }
+    const setProtocolValue = (path, value) => {
+        if (form.getValuesIn(path) !== value) {
+            form.setValuesIn(path, value);
+        }
+    };
+    setProtocolValue(`${VALUE_MAPPING_SCHEMA_KEY}.version`, VALUE_MAPPING_VERSION);
+    setProtocolValue(`${VALUE_MAPPING_SCHEMA_KEY}.adapter`, adapter);
+    setProtocolValue(`${VALUE_MAPPING_SCHEMA_KEY}.scope`, scope);
+    setProtocolValue(`${VALUE_MAPPING_SCHEMA_KEY}.submitSource`, submitSource);
+};
+/** 同步 target Field 的错误反馈；它不读取 feedback，因此 feedback 只是 reaction 输出。 */
+const syncValueMappingErrors = (form, targetPaths, targetValues, error, message) => {
+    targetPaths.forEach((path, index) => {
+        form.query(path).take((targetField) => {
+            if (!(targetField === null || targetField === void 0 ? void 0 : targetField.setSelfErrors))
+                return;
+            const hasInput = hasInputText(targetValues[index]);
+            const shouldShowError = Boolean(error && (error !== 'incomplete' || hasInput));
+            targetField.setSelfErrors(shouldShowError && message ? [message] : []);
+        });
+    });
+};
+/**
+ * 读取一次 target 快照。主 reaction 和延迟 cleanup 必须使用同一口径：优先读
+ * 已注册 Field 的 value，未注册的动态路径才从 Form values 兜底，避免 cleanup
+ * 看到的值与主 reaction 不一致。
+ */
+const readValueMappingTargetValues = (form, targetPaths) => targetPaths.map((path) => {
+    let hasField = false;
+    let fieldValue;
+    // 使用 take callback 兼容 Formily Query 和设置表单测试/动态节点实现。
+    form.query(path).take((targetField) => {
+        hasField = Boolean(targetField);
+        fieldValue = targetField === null || targetField === void 0 ? void 0 : targetField.value;
+    });
+    const fallbackValue = form.getValuesIn(path);
+    return hasField && fieldValue !== undefined ? fieldValue : fallbackValue;
+});
+/**
+ * 创建设置表单使用的 value-mapping 协议与校验 reaction。
+ *
+ * 协议和反馈必须由一个 autorun 编排。若分别挂两个 x-reactions，它们对同一
+ * 次 onInput 的调度顺序不稳定：协议 reaction 规范化数字路径时会再次写值，
+ * 校验 reaction 可能拿到中间快照，导致残留错误或覆盖刚写入的配置。本 reaction
+ * 先读取一次 targetValues，再同步反馈和协议，保证二者始终对应同一组输入。
+ *
+ * target 全空时先同步清除反馈，让界面立即恢复；父级协议延迟到当前 onInput/batch
+ * 结束后的 Promise 微任务再删除。微任务执行前会重新读取最新 target：若用户已快速
+ * 重新输入则跳过删除，避免旧 cleanup 误删。按 Form 隔离的 WeakSet 会合并同一 Form
+ * 的重复 cleanup，同时不会影响其它设置 Form。
+ */
+export const createValueMappingSettingsReaction = ({ adapter, targetPaths, scope = VALUE_MAPPING_RELATIVE_SCOPE, submitSource = false, getMessage, }) => {
+    return (_field, reactionScope) => {
+        const form = reactionScope === null || reactionScope === void 0 ? void 0 : reactionScope.$form;
+        if (!form)
+            return;
+        // 优先读取已注册 Field 的 value computed，让依赖绑定在稳定的 Field 上；协议
+        // 首次从数字路径对象规范化成数组后，后续另一个 Input 仍能触发同一 autorun。
+        // 未挂载的 target 则退回 Form values，兼容动态设置 Schema。
+        const targetValues = readValueMappingTargetValues(form, targetPaths);
+        const error = validateValueMappingTargetPaths(targetValues);
+        const message = error ? getMessage(error, reactionScope) : undefined;
+        const hasTarget = targetValues.some(hasInputText);
+        if (!hasTarget) {
+            // 反馈清理同步执行；只有协议确实存在时才排队父对象删除。
+            untracked(() => {
+                syncValueMappingErrors(form, targetPaths, targetValues, error, message);
+            });
+            if (form.getValuesIn(VALUE_MAPPING_SCHEMA_KEY) !== undefined &&
+                !pendingMappingCleanups.has(form)) {
+                pendingMappingCleanups.add(form);
+                Promise.resolve().then(() => {
+                    pendingMappingCleanups.delete(form);
+                    // 清空与重新输入可能发生在同一批次或连续微任务中，因此这里必须重新读值。
+                    const latestTargetValues = readValueMappingTargetValues(form, targetPaths);
+                    const latestHasTarget = latestTargetValues.some(hasInputText);
+                    if (!latestHasTarget &&
+                        form.getValuesIn(VALUE_MAPPING_SCHEMA_KEY) !== undefined) {
+                        form.deleteValuesIn(VALUE_MAPPING_SCHEMA_KEY);
+                    }
+                });
+            }
+            return;
+        }
+        // feedback 是输出，不能反过来成为依赖；协议写入则保留通知，使 autorun
+        // 在数字路径从对象规范化为数组后重新建立对新数组叶节点的依赖。
+        untracked(() => {
+            syncValueMappingErrors(form, targetPaths, targetValues, error, message);
+        });
+        syncValueMappingProtocol(form, targetValues, adapter, scope, submitSource);
+    };
+};

package/esm/locales/DatePicker.js

@@ -76,11 +76,41 @@ export const DatePicker = {
 export const DateRangePicker = createLocales(DatePicker, {
     'zh-CN': {
         title: '日期范围',
+        settings: {
+            'value-mapping-group': {
+                title: '数据映射',
+                startPath: '开始日期字段路径',
+                endPath: '结束日期字段路径',
+                incomplete: '开始和结束字段路径必须同时填写',
+                duplicate: '开始和结束字段路径不能相同',
+                invalid: '请输入合法的相对字段路径',
+            },
+        },
     },
     'en-US': {
         title: 'DateRange',
+        settings: {
+            'value-mapping-group': {
+                title: 'Data Mapping',
+                startPath: 'Start date field path',
+                endPath: 'End date field path',
+                incomplete: 'Both start and end field paths are required',
+                duplicate: 'Start and end field paths must be different',
+                invalid: 'Enter a valid relative field path',
+            },
+        },
     },
     'ko-KR': {
         title: '날짜범위 선택 상자',
+        settings: {
+            'value-mapping-group': {
+                title: '데이터 매핑',
+                startPath: '시작 날짜 필드 경로',
+                endPath: '종료 날짜 필드 경로',
+                incomplete: '시작 및 종료 필드 경로를 모두 입력하세요',
+                duplicate: '시작 및 종료 필드 경로는 달라야 합니다',
+                invalid: '올바른 상대 필드 경로를 입력하세요',
+            },
+        },
     },
 });

package/lib/components/DatePicker/preview.js

@@ -3,16 +3,54 @@ Object.defineProperty(exports, "__esModule", { value: true });
 exports.DatePicker = void 0;
 const antd_v5_1 = require("@formily/antd-v5");
 const core_1 = require("@formily-design/core");
-const Field_1 = require("../Field");
+const core_2 = require("@formily-design/core");
+const shared_1 = require("../Field/shared");
+const valueMapping_1 = require("../Field/valueMapping");
 const schemas_1 = require("../../schemas");
 const locales_1 = require("../../locales");
+const valueMappingTargetPaths = [
+    `${core_2.VALUE_MAPPING_SCHEMA_KEY}.targets.0.path`,
+    `${core_2.VALUE_MAPPING_SCHEMA_KEY}.targets.1.path`,
+];
+const createMappingPathSchema = (titleToken) => ({
+    type: 'string',
+    title: `{{$node.getMessage("settings.value-mapping-group.${titleToken}")}}`,
+    'x-decorator': 'FormItem',
+    'x-decorator-props': {
+        // SettingsForm 默认不展示 feedback；映射路径需要即时呈现输入校验结果。
+        feedbackLayout: 'loose',
+    },
+    'x-component': 'Input',
+    'x-component-props': {
+        allowClear: true,
+    },
+});
+const ValueMappingGroup = {
+    type: 'void',
+    'x-component': 'CollapseItem',
+    'x-component-props': { defaultExpand: false },
+    // 分组只挂一个 reaction，避免协议同步与反馈校验的两个 autorun 产生竞态。
+    'x-reactions': [
+        (0, valueMapping_1.createValueMappingSettingsReaction)({
+            adapter: 'tuple',
+            targetPaths: valueMappingTargetPaths,
+            scope: 'relative',
+            submitSource: false,
+            getMessage: (error, scope) => { var _a; return (_a = scope.$node) === null || _a === void 0 ? void 0 : _a.getMessage(`settings.value-mapping-group.${error}`); },
+        }),
+    ],
+    properties: {
+        [valueMappingTargetPaths[0]]: createMappingPathSchema('startPath'),
+        [valueMappingTargetPaths[1]]: createMappingPathSchema('endPath'),
+    },
+};
 exports.DatePicker = antd_v5_1.DatePicker;
 exports.DatePicker.Behavior = (0, core_1.createBehavior)({
     name: 'DatePicker',
     extends: ['Field'],
     selector: (node) => node.props['x-component'] === 'DatePicker',
     designerProps: {
-        propsSchema: (0, Field_1.createFieldSchema)(schemas_1.AllSchemas.DatePicker),
+        propsSchema: (0, shared_1.createFieldSchema)(schemas_1.AllSchemas.DatePicker),
     },
     designerLocales: locales_1.AllLocales.DatePicker,
 }, {
@@ -20,7 +58,9 @@ exports.DatePicker.Behavior = (0, core_1.createBehavior)({
     extends: ['Field'],
     selector: (node) => node.props['x-component'] === 'DatePicker.RangePicker',
     designerProps: {
-        propsSchema: (0, Field_1.createFieldSchema)(schemas_1.AllSchemas.DatePicker.RangePicker),
+        propsSchema: (0, shared_1.createFieldSchema)(schemas_1.AllSchemas.DatePicker.RangePicker, undefined, {
+            'value-mapping-group': ValueMappingGroup,
+        }),
     },
     designerLocales: locales_1.AllLocales.DateRangePicker,
 });

package/lib/components/Field/index.d.ts

@@ -1,2 +1,3 @@
 export * from './preview';
 export * from './shared';
+export * from './valueMapping';

package/lib/components/Field/index.js

@@ -16,3 +16,4 @@ var __exportStar = (this && this.__exportStar) || function(m, exports) {
 Object.defineProperty(exports, "__esModule", { value: true });
 __exportStar(require("./preview"), exports);
 __exportStar(require("./shared"), exports);
+__exportStar(require("./valueMapping"), exports);

package/lib/components/Field/shared.d.ts

@@ -1,4 +1,4 @@
 import { ISchema } from '@formily/json-schema';
 export declare const createComponentSchema: (component: ISchema, decorator: ISchema) => Record<string, ISchema | undefined>;
-export declare const createFieldSchema: (component?: ISchema, decorator?: ISchema) => ISchema;
+export declare const createFieldSchema: (component?: ISchema, decorator?: ISchema, additionalGroups?: Record<string, ISchema>) => ISchema;
 export declare const createVoidFieldSchema: (component?: ISchema, decorator?: ISchema) => ISchema;

package/lib/components/Field/shared.js

@@ -68,10 +68,10 @@ const createComponentSchema = (component, decorator) => {
     };
 };
 exports.createComponentSchema = createComponentSchema;
-const createFieldSchema = (component, decorator = schemas_1.AllSchemas.FormItem) => {
+const createFieldSchema = (component, decorator = schemas_1.AllSchemas.FormItem, additionalGroups = {}) => {
     return {
         type: 'object',
-        properties: Object.assign({ 'field-group': {
+        properties: Object.assign(Object.assign({ 'field-group': {
                 type: 'void',
                 'x-component': 'CollapseItem',
                 properties: {
@@ -174,7 +174,7 @@ const createFieldSchema = (component, decorator = schemas_1.AllSchemas.FormItem)
                         'x-component': 'Switch',
                     },
                 },
-            } }, (0, exports.createComponentSchema)(component, decorator)),
+            } }, additionalGroups), (0, exports.createComponentSchema)(component, decorator)),
     };
 };
 exports.createFieldSchema = createFieldSchema;

package/lib/components/Field/valueMapping.d.ts

@@ -0,0 +1,45 @@
+import type { IScopeContext, SchemaReaction } from '@formily/json-schema';
+import { VALUE_MAPPING_RELATIVE_SCOPE } from '@formily-design/core';
+import type { ValueMappingTargetValidationError } from '@formily-design/core';
+export type { ValueMappingTargetValidationError } from '@formily-design/core';
+export interface ICreateValueMappingSettingsReactionOptions {
+    /**
+     * 映射运行时使用的 adapter 名称，例如 tuple。
+     */
+    adapter: string;
+    /**
+     * 设置表单中 target path 输入框的完整数据路径。
+     *
+     * 注意：这里配置的是输入框在设置表单中的路径，而不是用户最终填写的
+     * startDate、address.provinceCode 等业务字段路径。
+     */
+    targetPaths: string[];
+    scope?: typeof VALUE_MAPPING_RELATIVE_SCOPE;
+    submitSource?: boolean;
+    /**
+     * 根据校验错误码返回当前语言的提示文案。scope 会透传 Formily
+     * reaction 的作用域，因此设置器可以使用 `$node.getMessage` 读取节点语言。
+     */
+    getMessage: (error: ValueMappingTargetValidationError, scope: IScopeContext) => string | undefined;
+}
+/**
+ * 校验一组手动输入的映射 target 路径。
+ *
+ * 空数组表示尚未启用映射；一旦任意路径有值，所有 target 都必须填写、合法且唯一。
+ * 该方法与具体组件数量无关，日期范围、省市区等配置界面均可复用。
+ */
+export declare const validateValueMappingTargetPaths: (paths: unknown[]) => ValueMappingTargetValidationError | undefined;
+/**
+ * 创建设置表单使用的 value-mapping 协议与校验 reaction。
+ *
+ * 协议和反馈必须由一个 autorun 编排。若分别挂两个 x-reactions，它们对同一
+ * 次 onInput 的调度顺序不稳定：协议 reaction 规范化数字路径时会再次写值，
+ * 校验 reaction 可能拿到中间快照，导致残留错误或覆盖刚写入的配置。本 reaction
+ * 先读取一次 targetValues，再同步反馈和协议，保证二者始终对应同一组输入。
+ *
+ * target 全空时先同步清除反馈，让界面立即恢复；父级协议延迟到当前 onInput/batch
+ * 结束后的 Promise 微任务再删除。微任务执行前会重新读取最新 target：若用户已快速
+ * 重新输入则跳过删除，避免旧 cleanup 误删。按 Form 隔离的 WeakSet 会合并同一 Form
+ * 的重复 cleanup，同时不会影响其它设置 Form。
+ */
+export declare const createValueMappingSettingsReaction: ({ adapter, targetPaths, scope, submitSource, getMessage, }: ICreateValueMappingSettingsReactionOptions) => SchemaReaction;

package/lib/components/Field/valueMapping.js

@@ -0,0 +1,122 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.createValueMappingSettingsReaction = exports.validateValueMappingTargetPaths = void 0;
+const reactive_1 = require("@formily/reactive");
+const core_1 = require("@formily-design/core");
+// 一个 Form 只允许排队一个 cleanup；WeakSet 不持有 Form 强引用，也不会串扰其它 Form。
+const pendingMappingCleanups = new WeakSet();
+const hasInputText = (value) => typeof value === 'string' && Boolean(value.trim());
+/**
+ * 校验一组手动输入的映射 target 路径。
+ *
+ * 空数组表示尚未启用映射；一旦任意路径有值，所有 target 都必须填写、合法且唯一。
+ * 该方法与具体组件数量无关，日期范围、省市区等配置界面均可复用。
+ */
+const validateValueMappingTargetPaths = (paths) => (0, core_1.validateValueMappingTargetPaths)(paths, { allowEmpty: true });
+exports.validateValueMappingTargetPaths = validateValueMappingTargetPaths;
+/** 将同一份 target 快照规范化为运行时协议。 */
+const syncValueMappingProtocol = (form, targetValues, adapter, scope, submitSource) => {
+    const normalizedTargets = targetValues.map((path) => ({
+        path: typeof path === 'string' ? path.trim() : '',
+    }));
+    const currentTargets = form.getValuesIn(`${core_1.VALUE_MAPPING_SCHEMA_KEY}.targets`);
+    const targetsChanged = !Array.isArray(currentTargets) ||
+        currentTargets.length !== normalizedTargets.length ||
+        normalizedTargets.some((target, index) => { var _a; return ((_a = currentTargets[index]) === null || _a === void 0 ? void 0 : _a.path) !== target.path; });
+    // FormPath 的数字点路径默认可能生成对象，这里统一规范化为运行时协议要求的数组。
+    if (targetsChanged) {
+        form.setValuesIn(`${core_1.VALUE_MAPPING_SCHEMA_KEY}.targets`, normalizedTargets);
+    }
+    const setProtocolValue = (path, value) => {
+        if (form.getValuesIn(path) !== value) {
+            form.setValuesIn(path, value);
+        }
+    };
+    setProtocolValue(`${core_1.VALUE_MAPPING_SCHEMA_KEY}.version`, core_1.VALUE_MAPPING_VERSION);
+    setProtocolValue(`${core_1.VALUE_MAPPING_SCHEMA_KEY}.adapter`, adapter);
+    setProtocolValue(`${core_1.VALUE_MAPPING_SCHEMA_KEY}.scope`, scope);
+    setProtocolValue(`${core_1.VALUE_MAPPING_SCHEMA_KEY}.submitSource`, submitSource);
+};
+/** 同步 target Field 的错误反馈；它不读取 feedback，因此 feedback 只是 reaction 输出。 */
+const syncValueMappingErrors = (form, targetPaths, targetValues, error, message) => {
+    targetPaths.forEach((path, index) => {
+        form.query(path).take((targetField) => {
+            if (!(targetField === null || targetField === void 0 ? void 0 : targetField.setSelfErrors))
+                return;
+            const hasInput = hasInputText(targetValues[index]);
+            const shouldShowError = Boolean(error && (error !== 'incomplete' || hasInput));
+            targetField.setSelfErrors(shouldShowError && message ? [message] : []);
+        });
+    });
+};
+/**
+ * 读取一次 target 快照。主 reaction 和延迟 cleanup 必须使用同一口径：优先读
+ * 已注册 Field 的 value，未注册的动态路径才从 Form values 兜底，避免 cleanup
+ * 看到的值与主 reaction 不一致。
+ */
+const readValueMappingTargetValues = (form, targetPaths) => targetPaths.map((path) => {
+    let hasField = false;
+    let fieldValue;
+    // 使用 take callback 兼容 Formily Query 和设置表单测试/动态节点实现。
+    form.query(path).take((targetField) => {
+        hasField = Boolean(targetField);
+        fieldValue = targetField === null || targetField === void 0 ? void 0 : targetField.value;
+    });
+    const fallbackValue = form.getValuesIn(path);
+    return hasField && fieldValue !== undefined ? fieldValue : fallbackValue;
+});
+/**
+ * 创建设置表单使用的 value-mapping 协议与校验 reaction。
+ *
+ * 协议和反馈必须由一个 autorun 编排。若分别挂两个 x-reactions，它们对同一
+ * 次 onInput 的调度顺序不稳定：协议 reaction 规范化数字路径时会再次写值，
+ * 校验 reaction 可能拿到中间快照，导致残留错误或覆盖刚写入的配置。本 reaction
+ * 先读取一次 targetValues，再同步反馈和协议，保证二者始终对应同一组输入。
+ *
+ * target 全空时先同步清除反馈，让界面立即恢复；父级协议延迟到当前 onInput/batch
+ * 结束后的 Promise 微任务再删除。微任务执行前会重新读取最新 target：若用户已快速
+ * 重新输入则跳过删除，避免旧 cleanup 误删。按 Form 隔离的 WeakSet 会合并同一 Form
+ * 的重复 cleanup，同时不会影响其它设置 Form。
+ */
+const createValueMappingSettingsReaction = ({ adapter, targetPaths, scope = core_1.VALUE_MAPPING_RELATIVE_SCOPE, submitSource = false, getMessage, }) => {
+    return (_field, reactionScope) => {
+        const form = reactionScope === null || reactionScope === void 0 ? void 0 : reactionScope.$form;
+        if (!form)
+            return;
+        // 优先读取已注册 Field 的 value computed，让依赖绑定在稳定的 Field 上；协议
+        // 首次从数字路径对象规范化成数组后，后续另一个 Input 仍能触发同一 autorun。
+        // 未挂载的 target 则退回 Form values，兼容动态设置 Schema。
+        const targetValues = readValueMappingTargetValues(form, targetPaths);
+        const error = (0, exports.validateValueMappingTargetPaths)(targetValues);
+        const message = error ? getMessage(error, reactionScope) : undefined;
+        const hasTarget = targetValues.some(hasInputText);
+        if (!hasTarget) {
+            // 反馈清理同步执行；只有协议确实存在时才排队父对象删除。
+            (0, reactive_1.untracked)(() => {
+                syncValueMappingErrors(form, targetPaths, targetValues, error, message);
+            });
+            if (form.getValuesIn(core_1.VALUE_MAPPING_SCHEMA_KEY) !== undefined &&
+                !pendingMappingCleanups.has(form)) {
+                pendingMappingCleanups.add(form);
+                Promise.resolve().then(() => {
+                    pendingMappingCleanups.delete(form);
+                    // 清空与重新输入可能发生在同一批次或连续微任务中，因此这里必须重新读值。
+                    const latestTargetValues = readValueMappingTargetValues(form, targetPaths);
+                    const latestHasTarget = latestTargetValues.some(hasInputText);
+                    if (!latestHasTarget &&
+                        form.getValuesIn(core_1.VALUE_MAPPING_SCHEMA_KEY) !== undefined) {
+                        form.deleteValuesIn(core_1.VALUE_MAPPING_SCHEMA_KEY);
+                    }
+                });
+            }
+            return;
+        }
+        // feedback 是输出，不能反过来成为依赖；协议写入则保留通知，使 autorun
+        // 在数字路径从对象规范化为数组后重新建立对新数组叶节点的依赖。
+        (0, reactive_1.untracked)(() => {
+            syncValueMappingErrors(form, targetPaths, targetValues, error, message);
+        });
+        syncValueMappingProtocol(form, targetValues, adapter, scope, submitSource);
+    };
+};
+exports.createValueMappingSettingsReaction = createValueMappingSettingsReaction;

package/lib/locales/DatePicker.js

@@ -79,11 +79,41 @@ exports.DatePicker = {
 exports.DateRangePicker = (0, core_1.createLocales)(exports.DatePicker, {
     'zh-CN': {
         title: '日期范围',
+        settings: {
+            'value-mapping-group': {
+                title: '数据映射',
+                startPath: '开始日期字段路径',
+                endPath: '结束日期字段路径',
+                incomplete: '开始和结束字段路径必须同时填写',
+                duplicate: '开始和结束字段路径不能相同',
+                invalid: '请输入合法的相对字段路径',
+            },
+        },
     },
     'en-US': {
         title: 'DateRange',
+        settings: {
+            'value-mapping-group': {
+                title: 'Data Mapping',
+                startPath: 'Start date field path',
+                endPath: 'End date field path',
+                incomplete: 'Both start and end field paths are required',
+                duplicate: 'Start and end field paths must be different',
+                invalid: 'Enter a valid relative field path',
+            },
+        },
     },
     'ko-KR': {
         title: '날짜범위 선택 상자',
+        settings: {
+            'value-mapping-group': {
+                title: '데이터 매핑',
+                startPath: '시작 날짜 필드 경로',
+                endPath: '종료 날짜 필드 경로',
+                incomplete: '시작 및 종료 필드 경로를 모두 입력하세요',
+                duplicate: '시작 및 종료 필드 경로는 달라야 합니다',
+                invalid: '올바른 상대 필드 경로를 입력하세요',
+            },
+        },
     },
 });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@formily-design/formily-antd",
-  "version": "1.0.20",
+  "version": "1.0.21",
   "license": "MIT",
   "main": "lib",
   "module": "esm",
@@ -24,7 +24,7 @@
     "start": "webpack-dev-server --config playground/webpack.dev.ts"
   },
   "devDependencies": {
-    "@formily-design/react-settings-form": "1.0.20",
+    "@formily-design/react-settings-form": "1.0.21",
     "@formily/antd-v5": "^1.2.4",
     "@formily/core": "^2.0.2",
     "@formily/json-schema": "^2.0.2",
@@ -69,14 +69,14 @@
     "react-is": ">=16.8.0 || >=17.0.0"
   },
   "dependencies": {
-    "@formily-design/core": "1.0.20",
-    "@formily-design/formily-setters": "1.0.20",
-    "@formily-design/formily-transformer": "1.0.20",
-    "@formily-design/react": "1.0.20",
-    "@formily-design/shared": "1.0.20"
+    "@formily-design/core": "1.0.21",
+    "@formily-design/formily-setters": "1.0.21",
+    "@formily-design/formily-transformer": "1.0.21",
+    "@formily-design/react": "1.0.21",
+    "@formily-design/shared": "1.0.21"
   },
   "publishConfig": {
     "access": "public"
   },
-  "gitHead": "c216e53994fe44a507f4360be8867c59b2f1b641"
+  "gitHead": "e0694bf3df21eeba42fa476affe8642d07fb3522"
 }