Before submitting a pull request, please make sure the following is done...

fix #4204

• Ensure the pull request title and commit message follow the Commit Specific in English.
• Fork the repo and create your branch from master or formily_next.
• If you've added code that should be tested, add tests!
• [] If you've changed APIs, update the documentation.
• Ensure the test suite passes (npm test).
• Make sure your code lints (npm run lint) - we've done our best to make sure these rules match our internal linting guidelines.

Please do not delete the above content

What have you changed?

description

This PR addresses the following issues and provides the following features:

• 1 Added the x-validator-merge attribute to tags for merging with global validation. Custom global validation is sometimes needed, but due to Formity’s previous design, global validation, like required, couldn’t have custom messages. Even if attributes are set in x-validator, they are added as additional rules rather than replacing the existing ones. The x-validator-merge attribute allows merging global and local validations.

• 2 Introduced the registerMergeRules API, which works similarly to registerValidateRules, allowing functions to override default global validation rules in Formity.

• 3 Distinguished the state of rules into four types, with the first three being mergeable and the last one overriding the previous ones (refer to packages/validator/src/registry.ts):

  • 3.1 Global validation
  • 3.2 Shorthand property validation: required, maximum, minimum
  • 3.3 Local validation (mergeable): Rules specified by x-validator-merge or registerMergeRules
  • 3.4 Validator: Rules specified by x-validator, which do not participate in merging operations, as determined by Ant Design's properties

• 4 Add the schema variable to the third function in the validation function. This helps in accessing schema information within custom validation functions. Previously, the context parameter was transformed by the SchemaStateMap variable in packages/json-schema/src/shared.ts, making it impossible for developers to retrieve information such as required, maximum, or minimum

registerMergeRules(api)

example

import React from 'react'
import { createForm, } from '@formily/core'
import {registerMergeRules} from "@formily/validator"
import { createSchemaField } from '@formily/react'
import { Form, FormItem, Input, NumberPicker } from '@formily/antd'

const form = createForm()

const SchemaField = createSchemaField({
  components: {
    Input,
    FormItem,
    NumberPicker,
  },
})
registerMergeRules({
  required:(e,ctx)=>{
    console.log(e, ctx)
    if(!e){
      return "jjjjjjjjjjjjjjj"
    }
  }
})
export default () => (
  <Form form={form} labelCol={6} wrapperCol={10}>
    <SchemaField>
      <SchemaField.String
        maximum={5}
        title={"d"}
        name="8"
        required
        x-component="Input"
        x-decorator="FormItem"
      />
    
    </SchemaField>
  </Form>
)

x-validator-merge(prop)

example

import React from 'react'
import { createForm, registerValidateRules,registerMergeRules } from '@formily/core'
import { createSchemaField } from '@formily/react'
import { Form, FormItem, Input, NumberPicker } from '@formily/antd'

const form = createForm()

const SchemaField = createSchemaField({
  components: {
    Input,
    FormItem,
    NumberPicker,
  },
})

export default () => (
  <Form form={form} labelCol={6} wrapperCol={10}>
    <SchemaField>
      <SchemaField.String
        maximum={5}
        name="8"
        required
         x-validator-merge={{
          required(value) {
              if (!value) return 'customer merge'
          }
         }}
        x-component="Input"
        x-decorator="FormItem"
      />
    
    </SchemaField>
  </Form>
)