[Bug Report] invoking form.setValues in FormStep results the different scenarios

[haoliangwu]

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

Reproduction link

Steps to reproduce

1. fill out the first step and click next button
2. then click back button

What is expected?

the input field with the name aaa should be empty because I invoke form.setValues in App.tsx@69.

What is actually happening?

the input field with the name aaa persisted with the previous value and the field.value has changed to it.

Package

@formily/[email protected]
@formily/[email protected]

---

Although I am not using FormStep directly, I implemented a similar one according to its source code and found this issue(maybe not).

After debugging, I found the root cause is as following:

• the FormStep invoke setDisplay method and update the filed.visible, see:

  formily/packages/antd/src/form-step/index.tsx

  Lines 81 to 83 in 2b8e705

  	if (name === currentStep.name) {
  	field.setDisplay('visible')
  	} else {

• the Field model reactive to this update and rollback the field value in caches, see:

  formily/packages/core/src/models/Field.ts

  Lines 246 to 250 in 2b8e705

  	if (display === 'visible') {
  	if (isEmpty(value)) {
  	this.setValue(this.caches.value)
  	this.caches.value = undefined
  	}

The reason I don't ensure whether this behavior is an issue is maybe it is designed deliberately, anyway, if we invoke form.setValues with non-empty values, it works as expected.

In this case, I think it is a little bit confusing for an empty string. Sometimes, the empty string also has a special meaning at the business level, maybe we should not fallback it simply by isEmpty assertion.

Note: I found similar issues, eg #2901, #2629 but not sure they are same.

[janryWang]

This logic of restoring the scene by default is specially designed. If you want not to go to the cache, you can call reset or manually clear the cache.