form 多重object rules验证失败

[wzohxia]

• I have searched the issues of this repository and believe that this is not a duplicate.

Version

ant-design-vue 2.0.0-rc.1

Environment

vue3.0.2 Chrome86.0.4240.75

Reproduction link

https://2x.antdv.com/components/form-cn/

Steps to reproduce

<template>
  <a-form :model="form" :rules="rules">
    <a-form-item label="测试" name="users.test">
      <a-input v-model:value="form.users.test" />
    </a-form-item>
  </a-form>
</template>

<script>
import { reactive, defineComponent, toRefs } from 'vue'
export default defineComponent({
  name: 'App',
  setup() {
    const info = reactive({
      form: { users: { test: '' } },
      rules: {
        'users.test': {
          required: true,
          message: '测试不能为空',
          type: 'string',
        },
      },
    })

    return {
      ...toRefs(info),
    }
  },
})
</script>

What is expected?

form验证结果正确

What is actually happening?

form验证结果无法消除

[tangjinzhou]

<template>
  <a-form :model="form">
    <a-form-item label="测试" :name="['users','test']" :rules="rules['users.test']">
      <a-input v-model:value="form.users.test" />
    </a-form-item>
  </a-form>
</template>

<script>
import { reactive, defineComponent, toRefs } from 'vue'
export default defineComponent({
  name: 'App',
  setup() {
    const info = reactive({
      form: { users: { test: '' } },
      rules: {
        'users.test': {
          required: true,
          message: '测试不能为空',
          type: 'string',
        },
      },
    })

    return {
      ...toRefs(info),
    }
  },
})
</script>

[tangjinzhou]

从 2.0 之后我们不再支持 点 的形式来连接字段 而是使用数组

[sososoyoung]

@tangjinzhou 帮忙把文档 https://2x.antdv.com/components/form-cn/#Form.Item 也更新下吧，我上次看文档也觉得应支持 array了（我以前是用react版本的），但是文档还是只有 string，容易误导，源码看确实已经支持了

ant-design-vue/components/form/FormItem.tsx

Line 82 in 8da63a6

name: { type: [String, Number, Array] as PropType<string | number | string[] | number[]> },

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.