Is it possible to override cache with post-processed `nuke_display` image?

[sureshjoshi]

I run some processing on an image in nuke_display (to get animated webps running), but I would like to then cache that and never re-run it as it's pretty time consuming.

I can't see how I would overwrite the existing cache URL/request from nuke_display - but I can effectively do something similar if I handle caching in my collectionView/application logic.

My hope is to move all this into a plugin, so other people can make use of this too.

Edit: For extra clarity on my question: nuke_display provides a UIImage and Data - and the existing in-memory cache (which I would like to re-use if possible) does not provide a url or an ImageRequest to update the cache on. I can always create a new cache key, that's not a problem - but separately keeping the unprocessed and processed items in cache (for only a few large animated images on my page) seems wasteful.

    override func nuke_display(image: UIImage?, data: Data?) {
        ...
        ImageCache.shared[???] = myProcessedImage
        ...
    }

This might also be a role for ImageProcess - but I'm still digging through the codebase to understand the pros/cons of that.

[kean]

Hey, nuke_display is a soft-deprecated API. If you take NukeUI.LazyImageView, it provides access to ImageContainer that has a userInfo dictionary where a decoder (ImageDecoding) or a processor (ImageProcessing) can attach any additional information you need to be cached.

In terms of rendering, I suggest looking for a solution similar to Gifu. I'm not sure if something similar exist for WebP.

I'm considering adding animated image rendering support on the NukeUI level, but nothing specific planned yet.