Skip to content
This repository has been archived by the owner on Jan 24, 2024. It is now read-only.

Bad caching strategy #20

Open
kevinbecxrra opened this issue May 30, 2022 · 0 comments
Open

Bad caching strategy #20

kevinbecxrra opened this issue May 30, 2022 · 0 comments

Comments

@kevinbecxrra
Copy link

kevinbecxrra commented May 30, 2022

The first caching structure identified consists in flutter_cache_manager. In this case, it is used to download and cache files in the cache directory of the app. Also, it uses cached_network_image since it is necessary to handle storage of user´s pictures of weekly Trinity College’s events. However, it uses a GitHub repository version as it is shown on figure. This can be a bad strategy since GitHub´s code is not public and cannot have the latest version which can cause troubles between the dependencies in future occasion. Also, this situation makes that users that has the code cannot execute the app because the repository is on other classes of the project.
Imagen1

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant