Remove old cached items about swr

[shuding]

Thanks @JakeCoxon that’s a good question! Yeah currently that’s the only way, because it might be dangerous to clear a cached key automatically: we don’t know if there’s any existing component still reading from that key.

To support that, we need to maintain a list for active keys (add/remove a key to the list when the SWR’s parent component is mounting/unmounted), which is not yet implemented.

Finally, we plan to export the cache APIs from the lib, and add options to the config soon. So you can override it with your own implementation like LRU cache, or just manipulate the cache object.

[hems]

Finally, we plan to export the cache APIs from the lib, and add options to the config soon. So you can override it with your own implementation like LRU cache, or just manipulate the cache object.

that sounds great!

[huozhi]

SWR 1.0 has a new feature that can create custom cache provider to apply your own logic of managing cache. But as @shuding 's the comment above, this is still pretty dangerous to do which could lead to inconsistence between UI and cache state.

[shuding]

I think a middleware and ref counting (#92) can work. I can build a prototype for this.

[shuding]

This middleware should work, maybe I can publish it as a package:

https://gist.github.com/shuding/915d6844db74e131ece951a2eff0f320

[piotr-cz]

@shuding The counter middleware removes key from cache, however the values corresponding to errorKey and isValidatingKey are still kept.