Baseflow / Baseflow/flutter_cache_manager
issue with the stalePeriod config
- 主要言語
- Dart
- スター
- 809
- フォーク
- 510
- 平均マージ
- 6分
- マージ済み PR(30日)
- 1
説明
I’ve encountered an issue with the stalePeriod setting in our CustomCacheManager when using it with cached_network_image. I tried setting different values, such as 1 minute, 1 day, and 15 days, but it doesn’t seem to take effect.
Here’s the current implementation:
```
class CustomCacheManager {
static const key = 'customCacheKey';
static CacheManager instance = CacheManager(
Config(
key,
stalePeriod: const Duration(days: 15),
),
);
}
```
I expected the cache to expire based on the stalePeriod value, but the images are still being loaded from cache beyond the set duration. Are there any limitations or additional configurations required for cached_network_image to respect this setting?
Would appreciate any insights. Thanks!
cached_network_image: ^3.4.1
flutter_cache_manager: ^3.4.1
flutter: 3.29.2
コントリビューションガイド
調査の方向性
Start by reproducing the behavior with the shown CustomCacheManager class and its Config.stalePeriod value alongside cached_network_image. Trace how the cache manager is supplied to image loading and verify whether an image remains usable after the configured duration. Done means identifying the cause and making stalePeriod take effect, or documenting a confirmed limitation and required configuration.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- dart, flutter
- 領域
- mobile-dev
- issue の種類
- バグ
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 活発さ
- 停滞
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 25/100