Custom Age Threshold On Cache Objects Over Capacity

Open
#507 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
dart, flutter
Domain
mobile

Research direction

Locate Config and getObjectsOverCapacity, then trace where the hardcoded one-day Duration is used during cleanup. Add the optional duration while preserving the one-day default, support custom values such as 12 hours, and verify cache cleanup still respects the configured threshold.

Written by the indexing model from the issue text.

Description

🏗 Enhancement Proposal

Allow configuring the age threshold used when cleaning up cache objects over capacity.

Pitch

Currently, getObjectsOverCapacity uses a hardcoded Duration(days: 1) to filter which cached objects are eligible for removal during cleanup. This means objects touched within the last 24 hours are never removed, even if the cache exceeds its capacity.

This can be problematic in scenarios where:

  • Apps have high cache turnover and need more aggressive cleanup (e.g., Duration(hours: 6))
  • Apps want to preserve recently accessed items for longer periods (e.g., Duration(days: 7))
  • The 1-day threshold doesn't align with the app's usage patterns

Proposed solution:

Add an optional maxCapacityAgeFilterDuration parameter to Config that allows developers to customize this threshold. The parameter defaults to Duration(days: 1) to maintain backward compatibility.

CacheManager(
  Config(
    'customCacheKey',
    maxCapacityAgeFilterDuration: Duration(hours: 12), // Only remove items untouched for 12+ hours
  ),
);

This gives developers fine-grained control over cache eviction behavior without changing the default experience.

Platforms affected (mark all that apply)
  • 📱 iOS
  • 🤖 Android
Dominant language
Dart
Stars
810
Forks
510
Avg merge
2d 2h
Merged PRs (30d)
11

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Baseflow/flutter_cache_manager

All issues in Baseflow/flutter_cache_manager

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.