Baseflow / Baseflow/flutter_cache_manager
Cache eviction
- Dominant language
- Dart
- Stars
- 809
- Forks
- 510
- Avg merge
- 6m
- Merged PRs (30d)
- 1
Description
Hi, thank you for a great project simplifying persistent caching in flutter!
## 🚀 Feature Requests
Eviction based on cache size. It seems the only policy available is number of objects and age.
### Contextualize the feature
I only store immutable objects. No object can ever change. It therefore does not make sense to me to evict objects based on age. I wish that the user can set a maximum allowed storage capacity for the cache, such as 250MB and then fill this up, never evicting until the cache is full. Never evicting could also be important to make offline mode work smoother, though I realize offline support might be outside the scope of this project.
### Describe the feature
### Platforms affected (mark all that apply)
- [X] :iphone: iOS
- [X] :robot: Android
Contributor guide
Research direction
Start by locating the existing cache eviction logic for object count and age, then inspect how cache configuration is exposed. Define how a configurable maximum storage capacity should interact with the current policies, and cover the behavior for iOS and Android with tests before considering the feature done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100