Baseflow / Baseflow/flutter_cache_manager
stalePeriod clarification
- Lenguaje dominante
- Dart
- Estrellas
- 809
- Forks
- 510
- Merge medio
- 6 min
- PR fusionados (30 d)
- 1
Descripción
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?
Guía de contribución
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- dart
- Área
- documentation
- Tipo de issue
- Documentación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 25/100