I've noticed that there are some layout differences between SwiftUI.Image and NukeUI.Image when using maxWidth/maxHeight in a List. I'm not sure if it's intentional or not, but it definitely caught me by surprise when I was comparing AsyncImage and LazyImage behaviour.
I've also noticed that the NukeUI.Image can cause sibling Text to truncate after a containing HStack appears after being scrolled offscreen. Sample code and screenshots below. The image used was downloaded from https://picsum.photos/id/0/5616/3744
Xcode: 13.4.1
iOS 15.5
import SwiftUI
import NukeUI
struct ContentView: View {
var body: some View {
List {
HStack {
NukeUI.Image(UIImage(named: "laptop")!)
.resizingMode(.fill)
.frame(width: 100, height: 100)
Text("Nuke - frame(width: 100, height: 100):")
}
HStack {
SwiftUI.Image(uiImage: UIImage(named: "laptop")!)
.resizable()
.frame(width: 100, height: 100)
Text("SwiftUI - frame(width: 100, height: 100):")
}
HStack {
NukeUI.Image(UIImage(named: "laptop")!)
.resizingMode(.fill)
.frame(maxWidth: 100, maxHeight: 100)
Text("Nuke - frame(maxWidth: 100, maxHeight: 100):")
}
HStack {
SwiftUI.Image(uiImage: UIImage(named: "laptop")!)
.resizable()
.frame(maxWidth: 100, maxHeight: 100)
Text("SwiftUI - frame(maxWidth: 100, maxHeight: 100)")
}
HStack {
Rectangle()
.frame(width: 100, height: 800)
Text("A long rectangle")
}
}
}
}


I've noticed that there are some layout differences between
SwiftUI.ImageandNukeUI.Imagewhen usingmaxWidth/maxHeightin aList. I'm not sure if it's intentional or not, but it definitely caught me by surprise when I was comparingAsyncImageandLazyImagebehaviour.I've also noticed that the
NukeUI.Imagecan cause siblingTextto truncate after a containingHStackappears after being scrolled offscreen. Sample code and screenshots below. The image used was downloaded fromhttps://picsum.photos/id/0/5616/3744Xcode: 13.4.1
iOS 15.5