You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because the default cachekey is encoded using URL, a different URL for the same image will invalidate the caching strategy.
I would like to be able to set a consistent cacheURL policy where images are cached with the URI of the image as the key instead of the URL.
I would like to be able to specify the cacheKey generation strategy for Kingfisher once when the App starts, instead of specifying the cacheKey strategy every time the images are downloaded and loaded.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The link to the image returned by the server will have a timestamp parameter.
That is, for the same image, the URIs will be the same, but the URLs will be different,For example:
https://www.baidu.com/img/PCtm_d9c8750bed0b3c7d089fa7d55720d6cf.png?timestamp=1692946226
https://www.baidu.com/img/PCtm_d9c8750bed0b3c7d089fa7d55720d6cf.png?timestamp=1692946556
Because the default cachekey is encoded using URL, a different URL for the same image will invalidate the caching strategy.
I would like to be able to set a consistent cacheURL policy where images are cached with the URI of the image as the key instead of the URL.
I would like to be able to specify the cacheKey generation strategy for Kingfisher once when the App starts, instead of specifying the cacheKey strategy every time the images are downloaded and loaded.
Beta Was this translation helpful? Give feedback.
All reactions