-
-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
feat(KeepAlive): support matchBy + allow custom caching strategy #3414
feat(KeepAlive): support matchBy + allow custom caching strategy #3414
Conversation
I think this should go through an RFC first to explore the different possible APIs, e.g. we could also only match by key if another prop is passed |
Agree, there is still an issue requesting the management of the cache, also this #1518 |
Для продолжения жду vuejs/core#3414
这个啥时候能用上呢 |
I don’t like Vue’s KeepAlive cache policy , So I want to create a component like KeepAlive. |
同问 |
Is there any progress? |
Close: #2084This PR allowsKeepAlive
to use thevnode.key
as the matching name, but the component's name still has a higher priority, which can avoid introducing breaking changesWriting RFC.....Edit: RFC vuejs/rfcs#284