-
-
Notifications
You must be signed in to change notification settings - Fork 505
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ExtendedImage.network(cacheMaxAge:Duration(days:1)) #504
Comments
extended_image: ^6.2.1 |
When the “cacheMax” is set, the picture reaches the expected effect and cannot be loaded. But the size of the acquired disk does not change. |
cacheMaxAge means cache image to disk, if over it, we will remove cache file and load it from network age. |
Can you change the behaviour slight to check for the URL to be present/available first, before you delete the expired cacheMaxAge ? Reason is that device could be offline/away from the network and the image might be not available (due to network unavailability) and even though the cache has expired (time wise), unless you can reload the image from the network, it should still be used. |
i will take a look later |
even loading image from cache takes so much time. |
cacheMaxAge When the time is up, the picture cannot be loaded, which is expected. However, the disk size has not changed
The text was updated successfully, but these errors were encountered: