MarcelGarus / MarcelGarus/flutter_cached

Caching strategies

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

Nobody has claimed this yet.

Dominant language
Dart
Stars
16
Forks
2
PR merge metrics
No merged PRs in 30d

Description

As @marcelgarus already said in https://github.com/marcelgarus/flutter_cached/issues/5#issuecomment-598095137:
> Actually, the current behavior is somewhat intended as a temporary behavior. In the long term, I was thinking about implementing multiple caching strategies that you can choose from (for example, only fetching the first time or fetching only if the last fetch is some amount in the past)

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by reading issue #5 and the quoted comment, which describe the current temporary caching behavior and possible future strategies. The issue does not name files, tests, or a settled strategy; done would require agreed behavior for selectable strategies such as fetching only once or refreshing after a specified interval.

Written by the indexing model from the issue text.

Assessment

Tech stack
dart, flutter
Domain
mobile-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.