fix(runtime-core): optimize the order of keys in mergeProps #11883
+19
−0
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.
fix #11880
The cause of this bug is that during the execution of
mergeProps
,my-info="default 1"
first addsmy-info
toprops
, thenv-bind="{ myInfo: 'default 2', 'my-info': 'Some value' }"
addsmyInfo
toprops
and updates the value ofmy-info
(but does not change the order of the keys). During rendering, the keys inprops
are rendered in the order they were added. SincemyInfo
was added aftermy-info
, the final rendered value is that ofmyInfo
.Therefore, during the execution of
mergeProps
, the order of keys corresponding to later updates should always remain at the end.