fix(compiler-core, runtime-core): fix unexpected render in v-for & v-memo #10431
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.
This PR fixes the unexpected render when
v-memo
is used in a keyedv-for
list. In the past, we just used an array as therenderCache
of a list whatever if it is keyed. This PR adds a map that usesnodes.key
as key andnode
as the value to the cache. When updates, if a list is keyed, it will check the cache from the map, so that can prevent unexpected render.close #10392