Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conditionally keep-alive component cache goes wrong when 'include' prop dynamically changes #4633

Closed
shidianxia opened this issue Jan 3, 2017 · 3 comments

Comments

@shidianxia
Copy link

Vue.js version

2.1.8 with vue-router 2.1.1

Reproduction Link

https://jsfiddle.net/shidianxia/ckj7xbqq/

Steps to reproduce

a -> b -> c -> Back (b) -> Back(a) -> b -> c -> Back(b)

What is Expected?

b is cached and enter into activated lifecycle
Component "a,b" Cached

What is actually happening?

b is cached but mounted a new one
Component "a,b,b" Cached

@LinusBorg
Copy link
Member

You might have wanted to mention that you change includeall the time. that looks complicated to track :D

@shidianxia
Copy link
Author

@LinusBorg Yes,I'd like to cache the components so I can see the cached content when I hit the back button. But I want to destroy the last component in order to re-render it when I enter again.
I'm not sure if I had describe my situation clearly 😂

@shidianxia
Copy link
Author

Thanks for the update!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants