Repository navigation
Conversation
kean
force-pushed
the
docs/recipes-and-coming-from
branch
2 times, most recently
from
November 1, 2026 15:36
9372ccd to
be9627c
Compare
This was referenced Nov 1, 2026
Fallback, Low Data Mode, per-request lifetime, pinning, memory limits, and HDR each have an answer that needs no new API, but none of them was written down. Retrying is left to the retry policy.
kean
force-pushed
the
docs/recipes-and-coming-from
branch
from
November 3, 2026 00:51
be9627c to
280310b
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Seven features that Kingfisher or SDWebImage have as options have a working answer in Nuke that was never written down. This adds a Recipes article for them, and a Coming From Another Library article that maps 53 Kingfisher, SDWebImage, and
AsyncImageAPIs to Nuke, with what has no counterpart. Docs only, no API.The seven gaps are the
reciperows in the feature table of report 06: retry, fallback sources, Low Data Mode, per-request expiration, pinning, a decode memory limit, and HDR.Proof
RecipesSnippets.swiftfrom this PR, unchanged, ran in a scratch package on an iOS 27.0 simulator, against a stubDataLoadingwith scripted failures. 12 tests in 1 suite passed, twice. The only substitution was shorter retry delays.primary, mirror1, mirror2, cached under the primaryURLErrorwith.constrainedhires, lowres, image deliveredisConstrainedtrue, then the low-data URL. Nothing cached under the full-size URLttl0.2 sDataCache, pinned cache has sweeps offmaxPixelSize3965isHighDynamicRangetrueHDRDecoderisHighDynamicRangetrueThe HDR run changed the recipe. The report expected a custom decoder for all HDR, but on iOS an image that's HDR in itself survives the default pipeline, because
preparingForDisplay()keeps its depth. So the decoder is now only for gain maps.Checks on the articles:
Tests/DocumentationSnippetsmake snippets, iOSllms-api.txtgrepin Kingfisher 8.14.0, SDWebImage 5.21.7, and SDWebImageSwiftUI 3.1.4 sources. TheAsyncImagerows come from report 06, which read the iOS 27.1 SDKNukerateLimiteris the existing onemake llms,--checkARTICLE_ORDERNot verified:
RetryableImage,AvatarView,LowDataImage) are compiled only. The logic behindLowDataImageran, without the view.HDRDecoderhas not seen a gain map. I couldn't encode one on the simulator (three attempts withkCGImageDestinationEncodeToISOGainmap), so the article calls it a starting point. HDR ran on a simulator, not on an HDR display.allowedDynamicRange(.high)andpreferredImageDynamicRangeare from Apple's docs, and weren't watched on screen.