I cannot coexist Modal.confirm and AForm

[CNMathon]

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

Version

2.2.2

Environment

Vue Version: 3.1.4

Reproduction link

https://github.com/CNMathon/antdv-issue

Steps to reproduce

I write business code and call the relevant methods.

What is expected?

No warnings are displayed and ATable is displayed properly in AModal when I call "Modal.confirm".

What is actually happening?

It reports a warning like the following:
[Vue warn]: resolveComponent can only be used in render() or setup().
[Vue warn]: withDirectives can only be used inside render functions.

[github-actions]

Hello @CNMathon. Please provide a online reproduction by forking this link for vue2、 link for vue3 or a minimal GitHub repository. Make sure to choose the correct version.

你好 @CNMathon, 我们需要你提供一个在线的重现实例以便于我们帮你排查问题。你可以通过点击 此处 for vue2、 此处 for vue3 创建一个 codesandbox 或者提供一个最小化的 GitHub 仓库。请确保选择准确的版本。

[CNMathon]

@tangjinzhou
I have created a minimized Github repository. You can navigate to it by clicking here.

[tangjinzhou]

1、Modal.confirm will use new createApp，you can not use a-form a-form-item ... register at app.vue
2、v-model-value not correct, you can visit https://github.com/vuejs/jsx-next find api
3、we recommend use in template，unless you have to leave the appcontext

[CNMathon]

@tangjinzhou
But if we write in a template, it will make us need to manage a lot of states. And you know, in fact, many states in modal are used temporarily.

[tangjinzhou]

<a-modal :key="String(visible)"></a-modal>

you can get new modal every time

[CNMathon]

<a-modal :key="String(visible)"></a-modal>

you can get new modal every time

@tangjinzhou I've tried this, but it causes the closing animation to fail.

[tangjinzhou]

<a-modal :key="String(visible)"></a-modal>

you can get new modal every time

@tangjinzhou I've tried this, but it causes the closing animation to fail.

那就换个和 visible 无关的 key，visible 的时候更换一个新的key，关闭的时候不变

[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.