Auto Extend the cached file's longevity if the user views it before it expired.

Open
#445 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
dart, flutter
Domain
mobile

Research direction

No files, tests, or entry points are identified. Start by locating the cache expiration and eviction paths in the repository, then resolve the option's API and renewal semantics. Done means viewed files renew their lifetime while unviewed files are removed after expiry, with tests covering both behaviors.

Written by the indexing model from the issue text.

Description

Auto Extend Longevity (Maybe Boolean)

an option to auto-extend the cached file's expiration date or longevity.

Contextualize the feature

It would be great, since, for example, like my application, I want to extend the longevity of a cached file every time a user views it. So, that it wouldn't cost me a lot with database: Bandwidth.

Describe the feature

Maybe add an option to enable the auto-extend longevity option, so that every time a user views a file its longevity time is extended. For example, I've set my file's longevity to 3 days. If the user views this file on day 2, a day before expiration, the expiration date will be extended by 2 days. Now the file would expire 3 days after the user viewed it. It would continue extending the expiration date and longevity unless a user hasn't viewed this file for 3 consecutive days.

This would help greatly if the application we're implementing it in is a social media type or e-commerce. We can cache the images and auto-extend their expiration date every time a user views them. But please make sure that the file is removed after the expiration date is over.

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.