Baseflow / Baseflow/flutter_cache_manager

stalePeriod clarification

Ouverte
#283 15 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
Dart
Étoiles
809
Forks
510
Merge moyen
6 min
PR mergées (30 j)
1

Description

i used to think that maxAgeCacheObject, which was i guess replaced with stalePeriod worked like so:
we download file -> mark some expiry date for it -> when it's expired we redownload it

with current docs it seems that's not the case
https://github.com/Baseflow/flutter_cache_manager/blob/46f0a0466d62350b48a520a5561fd59e0c546dda/flutter_cache_manager/lib/src/cache_manager.dart#L32-L33

so if i have stalePeriod that equals to 1 day and user opens my app each 12 hours, for instance, and the file is being reused, my cache will never be invalidated? if that's true, how do i change this?

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Read the cited lines in flutter_cache_manager/lib/src/cache_manager.dart and compare their stalePeriod wording with the current documentation. Clarify whether reuse refreshes or invalidates the cache, and document how a user can obtain the requested behavior if supported. The long-unanswered thread means the expected resolution is not established.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
dart
Domaine
documentation
Type d'issue
Documentation
Difficulté
2/5
Temps estimé
1-3 heures
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
25/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.