fix(runtime-core): ensure props definition objects are not mutated during props normalization (close: #6915) #6916
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.
During Props normalization, we add a couple of flags to the definition object for internal purposes, so this:
becomes this:
The problem is that we do this to the original object provided by the developer in the component's options. This can lead to issues when the developer re-uses these objects in different places.
This PR makes a shallow copy of that object before adding those flags, so the original definition stays untouched.
close: #6915