In Under the Radar - WWDC2023 at 24:37 Josh Shaffer says "you don't even have to write @Relationship, we detect the relationships"

you can't because if the View containing the FetchRequest is re-init (because of a recompute of the parent View's body) any changes made to the sort within onChange are lost.

make the MTKView a lazy var in the Coordinator class and set mtkView.delegate = self when returning it. Return context.coordinator.mtkView from makeUIView. You'll find this pattern in PaymentButton.swift in Apple's Fruta sample. Unfortunately engineers of other frameworks don't get it quite right, e.g. Coordinator(self) is wrong because anyone who knows SwiftUI knows the View struct is immediately discarded.

Excellent, thanks for taking the time to let me know about this! It works exactly as I wanted but sadly the way the picker view controller is shown is still very buggy so I likely will still use my own version using UIViewControllerRepresentable. Very strange it is missing from the documentation, I'm guessing its because the doc parser is not smart enough to process an extension of View in SwiftUI framework when working on the PhotosUI framework - submitted feedback FB11434717.

I think the async methods are just auto-generated by Swift, I don't think they actually coded anything. Also they don't support task cancellation so pretty useless for SwiftUI's task modifier.

Great tip, fixed my problem in development when changing from data to package and it was still being considered a folder by Finder and the app, even newly saved documents.

Because persistent history tracking transactions take up space on disk