-
-
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): expose pruneCacheEntry and add key match support on exclude/include changed in pruneCache. #5105
base: main
Are you sure you want to change the base?
Conversation
…ter 判断,增加对基于 component key 的 match 判断支持,以在 include, exclude 的 watch 回调中提供对应支持
Note: it's very similar to #4339 |
Yes, there are so many developers need and talk about this feature, and it is strange there is no progress so far. and like what you said, it is smallest, this pr or even a half of this pr is enough.
Did you mean the key match support in this pr? I just want to provide another way, In my opinion,
I am not good at that, and I will try later. |
Current 3.2 In the 26 version, KeepAlive's exclude still does not support key. When it comes to the effective process of exclude, he will still match the routing name, or is it using other ways to make key control the cache of routing? |
Yep, the current version of vue can't. I mean that this pr seems supported, but I haven't really tried😁 |
I'm sorry to misunderstand your idea |
Never mind, bro |
Hoping more progress on this PR :D ~~~ |
So, we can
this.$refs.keepAlive.pruneCacheEntry('COMPONENT_NAME/KEY')
;