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
Apologies if this already exists, but I couldn't find a reference anywhere in the docs, and I'm unclear as to the order of ops when it comes to loading cached items vs. the placeholder images. As far as I'm aware, calling the following:
will cause the library to load the placeholder image and attempt to make a network call. If the call succeeds it will use that item, otherwise it falls back to the cache.
Is there any way to configure the PINRemoteImageManager or the PINCache to always check the cache first and load any image found there before going to the network? This would greatly reduce the number of times that my placeholder image is shown.
I can reach into the cache myself, but I figure I'd check if its natively supported before doing so.
The text was updated successfully, but these errors were encountered:
Apologies if this already exists, but I couldn't find a reference anywhere in the docs, and I'm unclear as to the order of ops when it comes to loading cached items vs. the placeholder images. As far as I'm aware, calling the following:
will cause the library to load the placeholder image and attempt to make a network call. If the call succeeds it will use that item, otherwise it falls back to the cache.
Is there any way to configure the
PINRemoteImageManager
or thePINCache
to always check the cache first and load any image found there before going to the network? This would greatly reduce the number of times that my placeholder image is shown.I can reach into the cache myself, but I figure I'd check if its natively supported before doing so.
The text was updated successfully, but these errors were encountered: