fix(keep-alive): cache what is really needed not the whole VNode… - #9962
Closed
zrh122 wants to merge 1 commit into
Closed
fix(keep-alive): cache what is really needed not the whole VNode…#9962zrh122 wants to merge 1 commit into
zrh122 wants to merge 1 commit into
Conversation
zrh122
force-pushed
the
refactor-keepalive
branch
2 times, most recently
from
May 29, 2019 07:22
727875e to
7325696
Compare
zrh122
force-pushed
the
refactor-keepalive
branch
from
May 29, 2019 07:37
7325696 to
b694d93
Compare
13 tasks
|
Any update on when we can expect this PR to be merged? |
|
Can we have an update when this going to be merged? shouldnt this be |
|
I just noticed this bug too. The kept-alive node is not being destroyed. This is such a critical bug for a core component that's used by many |
which version had fixed the bug ?? |
|
Any news? |
Member
This file contains hidden or 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
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.
cache what is really needed not the whole
VNodedata. it also fixes #9842Fixes #2549
Fixes #9972
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
devbranch for v2.x (or to a previous version branch), not themasterbranchfix #xxx[,#xxx], where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information: