initialValue is being reset on change when ResetForm is called

[ellismonva]

What happened?

When calling the ResetForm, such as below:
resetForm({ values: { criteria: { card_type: 1 } } });;

This changes the initial value, which is correct, but then once I change my value in my form field again in my UI (such as updating to 2), it is changing the initialValue to the current value (in this case 2). I don't want initialValue to update on change, only when I call the resetForm function.

Version

Vue.js 3.x and vee-validate 4.x

What browsers are you seeing the problem on?

• Firefox
• Chrome
• Safari
• Microsoft Edge

Relevant log output

No response

Demo link

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[logaretm]

Please provide a demo on codesandbox for this issue

[ellismonva]

Hi @logaretm

Sandbox

There are three examples here. The functionality on nonNestedInput is what we expect in output.

valueNestedInputX and valueNestedInputY are acting as incorrect and different to nonNestedInput.

Why are they acting incorrectly?

After clicking 'Reset form' and once you change the value for either valueNestedInputX or valueNestedInputY (in the UI), the initialValue for these changes to be the same as the current value (which is incorrect) - note that in the nonNestedInputMeta, this does not change when the valueNonNestedInput changes.

[logaretm]

Thank you for reporting this, the issue was caused by the good old reference type not being cloned before assignment which means both the current input and initial value operated on the same values.

The fix should be out in the next patch for 4.4.x and 4.5-alpha.x releases.

[ellismonva]

Thanks @logaretm this is great news. I wanted to just point out something from the sandbox which may have gone unnoticed - im not sure if your fix would have addressed this..

In the first screenshot below, the initial values seem to be registered correctly, however when I click reset form, there is an additional 'input.y' added in the meta.

[logaretm]

When dealing with values, you cannot specify paths. So input.y won't target that field. Instead, provide the entire object like input.x in your example. So this is expected.

[ellismonva]

Ok, understood. Thanks @logaretm