feat(keepAlive): expose pruneCacheEntry and add key match support on exclude/include changed in pruneCache.

[Riant]

So, we can

1. Delete the cache use this.$refs.keepAlive.pruneCacheEntry('COMPONENT_NAME/KEY');
2. Include/Exclude components with not only component name but also component key.

[caozhong1996]

Note: it's very similar to #4339
I love this pr, only a small change which is enough for the demand. But I have a question, it seems that we can control cache via key now, why do we need expose pruneCacheEntry? Can you add some test?

[Riant]

@caozhong1996

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.

it seems that we can control cache via key now

Did you mean the key match support in this pr? I just want to provide another way, In my opinion, this.$refs.keepAlive.pruneCacheEntry('xxxx') is more visually and simple then this.exclude = ['xxxx']; this.$nextTick(() => this.exclude = []).

Can you add some test?

I am not good at that, and I will try later.

[huangqian0310]

@caozhong1996

it seems that we can control cache via key now

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？

[caozhong1996]

Yep, the current version of vue can't. I mean that this pr seems supported, but I haven't really tried😁
https://github.com/vuejs/vue-next/pull/5105/files#diff-28ccce6931cf4b4364f58400b93e2ae8efe180a82f885444bb5704574025a4d0L182-R183

[huangqian0310]

是的，当前版本的 vue 不能。我的意思是这个公关似乎受支持，但我还没有真正尝试过😁 https://github.com/vuejs/vue-next/pull/5105/files#diff-28ccce6931cf4b4364f58400b93e2ae8efe180a82f885444bb5704574025a4d0L182-R183

I'm sorry to misunderstand your idea

[caozhong1996]

Never mind, bro