Try to reproduce by forking https://codesandbox.io/s/quizzical-carson-z4kjnl and change typescript version in package.json

Hello @AndreiTS. Please provide a online reproduction by forking codesandbox of antd@5.x or antd@4.x, or provide a minimal GitHub repository. Issues labeled by Need Reproduce will be closed if no activities in 3 days.

你好 @AndreiTS, 我们需要你提供一个在线的重现实例以便于我们帮你排查问题。你可以通过点击这里创建一个 antd@5.x 或 antd@4.x 的 codesandbox，或者提供一个最小化的 GitHub 仓库。3 天内未跟进此 issue 将会被自动关闭。

@afc163 here is a minimal reproduction: https://github.com/AndreiTS/antd-setFieldsValue-typescript

this problem occurs because of this RecursivePartial implementation:

react-component/field-form#592 @kiner-tang 帮忙看看

react-component/field-form#592 @kiner-tang 帮忙看看

我看看

@kiner-tang changing any to T is better but don't fix the original issue: typescript playground

@kiner-tang changing any to T is better but don't fix the original issue: typescript playground

That's because strictNullChecks is turned on by default, so you can turn it off and try again.

Could you support this option? It's turned on by default, and enabled is TypeScript is on strict mode

Could you support this option? It's turned on by default, and enabled is TypeScript is on strict mode

If you want to keep this option on, wouldn't it be better not to use 'null' in the type definition? You can use other types instead. This is due to strictNullChecks in Typescript, not our RecursivePartial tool

Yes, I can. I actually replaced all null by undefined in my project where it was complaining, but it is annoying and it's probably going to affect someone else. I think there are other RecursivePartial implementations that could help with this.

This issue also affects types from libraries:

In this case the only way to fix is setting strictNullChecks to false, which is not ideal.

Given the issue shown in the example above, I would like to reopen this issue and request a resolution