什么时候删除自定义校验函数的包装器？

validateRules 函数会对自定义校验函数进行包装，这导致无法全面接收由 async-validator 传递过来的参数，比如 source 和 options

全面接收参数的好处

1. 验证出错时，通过响应 options.messages.[customRule] 消息即可消费 messageVariables
2. 对于通过使用 ConfigProvider 做全局表单 validateMessages 提供了一致的地区语言方案
3. 更简洁的代码

目前的解决方案

通过使用 asyncValidator 属性来避开包装器

import type { FormInstance, NamePath, RuleRender } from 'rc-field-form/lib/interface';

type ValidateMessages = import('rc-field-form/lib/interface').ValidateMessages & {
  confirmed: string;
};

type RuleObject = import('rc-field-form/lib/interface').RuleObject & {
  asyncValidator: (
    rule: RuleObject,
    value: import('rc-field-form/lib/interface').StoreValue,
    callback: (error?: string) => void,
    source: Record<string, import('rc-field-form/lib/interface').StoreValue>,
    options: import('rc-field-form/lib/interface').ValidateOptions & { messages: ValidateMessages }
  ) => void | Promise<void | string>;
}

export function confirmed(name: NamePath): RuleRender {
  return ({ getFieldValue }: FormInstance): RuleObject => ({
    asyncValidator: (rule, value, done, source, options) =>
      done(!value || getFieldValue(name) === value ? undefined : options.messages.confirmed),
  });
}

使用示例

自定义验证器示例

Start in src/utils/validateUtil.ts at validateRules, then compare its custom-validator wrapping with the async-validator v3.0.3 callback signature. Review the linked custom validation example and verify that the eventual behavior exposes source and options while preserving validateMessages and messageVariables handling.