podusowski
Cache functionality enhancement
I think that walkers' cache system should be documented somewhere.
In my own application, I've been ignoring the .cache folder, but I'm starting to feel like i should be able to have a deeper control over it, such as limiting it's size, enabling/disabling it, or being able to clear it, at runtime.
Additionally, I would like to provide insights to the user what this folder does, how much space it takes up, or how many tiles are being cached at any given moment.
I intend this issue to be some kind of discussion or issue tracker about various cache related things, starting with the things I mentioned above
On disk cache is a bit tricky. On WASM, it's controlled by the browser. On native builds, it's backed (and limited) by http_cache crate. The builder for it is here. I din't dig much, but it seems that configuration is somehow limited.
