fix(runtime-core): ensure keep-alive deep-watches include/exlude props (fix #2550) #2551
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
to pick up changes when provided with a reactive array instead of a ref
Size report
|
LinusBorg
changed the title
|
Thanks, but I want to know how I can solve this problem in the existing version。 |
|
Return a fresh array instead of mutating the existing one. |
LinusBorg
added
has workaround
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We currently watch components like this:
watch(() => [props.include, props.exclude], ....)Which works when
include/excludeare eithe refs or receive immutable values.If either is a
reactive([]), the watch would not be triggered.Addind
deep: truefixes the issue.