fix(useVModel): clone set to true triggered infinite loop #3097
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before submitting the PR, please make sure you do the following
fixes #123
).Description
When set clone true, it triggered infinite loop
watch proxy
, and watch triggered emitwatch props[key!] will triggered
after step 1's emitwatch props[key!]
will set proxy.value a new cloned data, it will triggeredwatch proxy
again (step 1), then infinite loop happenedThe problem was not mentioned directly in issue #3062, but mentioned in the issue comment by [Sevody]
Additional context
🤖 Generated by Copilot at 81b4878
Improve
useVModel
performance and stability by avoiding redundant updates. Use a flagisUpdating
to control the proxy value and theemit
callback.🤖 Generated by Copilot at 81b4878