resetForm when data received in Update Form

[sschneider-ihre-pvs]

The scenario is simple, I have an edit button on a record that opens a dialog to edit an address. When the component is mounted the data is fetched so I cannot use the result for the initialValues of useForm.
When I use resetForm({ values: result.value.address }) the console gets flooded with errors like:

Uncaught (in promise) TypeError: proxy must report the same value for the non-writable, non-configurable property

for some of the nested values in result.value.address.
I tried to use markRaw but then again it cannot add the __v_skip to it since it is not configurable.
I cannot pinpoint what exactly is the problem. The values that cause errors are objects that should pre select a selectbox with the value.

[sschneider-ihre-pvs]

Uncaught (in promise) TypeError: proxy must report the same value for the non-writable, non-configurable property
    traverse runtime-core.esm-bundler.js:1938
    traverse runtime-core.esm-bundler.js:1938
    getter runtime-core.esm-bundler.js:1760
    run reactivity.esm-bundler.js:190
    job runtime-core.esm-bundler.js:1801
    callWithErrorHandling runtime-core.esm-bundler.js:173
    flushJobs runtime-core.esm-bundler.js:406
    promise callback*queueFlush runtime-core.esm-bundler.js:298
    queueJob runtime-core.esm-bundler.js:292
    scheduler runtime-core.esm-bundler.js:1845
    triggerEffect reactivity.esm-bundler.js:400
    triggerEffects reactivity.esm-bundler.js:390
    trigger reactivity.esm-bundler.js:358
    set reactivity.esm-bundler.js:543
    validate vendor.js:74895
    applyFieldMutation vee-validate.esm.js:2109
    validate vendor.js:74895
    validate vendor.js:74878
    runLatest vee-validate.esm.js:464
    validateCurrentValue vee-validate.esm.js:1418
    validate vendor.js:74334
    runLatest vee-validate.esm.js:457
    resetField vee-validate.esm.js:1504
    validate vendor.js:75112
    applyFieldMutation vee-validate.esm.js:2109
    validate vendor.js:75010
    mutateAllFields vee-validate.esm.js:2112
    resetForm vee-validate.esm.js:2219
    .......

[logaretm]

I have never seen this before except for your earlier issue/discussion on it. Can you reproduce it in a minimal example so I can check what is going on?

We have tests covering the initial values and resetForm, so if this is a general problem it would be caught unless it is an edge case, an example would show.

[logaretm]

Is there something to regard to when trying to set values of select fields maybe?

Not that I can think of, no special cases for setting values in any way.

I also get a mismatch between the data that vee-validate shows in the plugin and what is in the form

Probably related, if I had to guess it is because something is up with the value you are passing to vee-validate. Either it is not a normal object or something else is going on. Not saying it is not a bug, but could be some cases that I may have overlooked. Again, it was never reported before for such a simple scenario.

Is there a way to debug such things?

Yep, an example would allow me to debug it. Otherwise, I'm just guessing which isn't ideal.

there are also properties missing, such a mess

I understand the frustration. But without an example, I can't help.

[sschneider-ihre-pvs]

I know an example would help but since it is all private/internal that is no easy task. At least I found one problem with having not matching attribute names

[sschneider-ihre-pvs]

I guess I have to first clean up my mess :D I will come back if I have more information

[sschneider-ihre-pvs]

@logaretm ok I think I found something. if (!isEqual(a[key], b[key])) if a and/or b is a proxy although there is key on both proxies this crashes with the error from above, why I do not know

[sschneider-ihre-pvs]

would it make sense to make toRaw(a)[key] an option ?