@WeagleWeagle I have a scenario in which the initialiser to the view passes a value and depending on the value I need to determine the predicate and sort descriptors. Currently I have an if else statement and then I am setting self._items as suggested by @aharriscrowne For that scenario, is it ok to set self._items in the initialiser?

IMHO it would be best to define what you are testing. If you are testing business logic, then it would be best to test only the model without SwiftUI code. You can be guaranteed the dependent views will change when the model changes

If you are new to SwiftUI it might be best to invest some time understanding the fundamentals of SwiftUI. It is different from UIKit, if you invest time up front you would save time on the long run. WWDC has some great content for SwiftUI, you could start with https://developer.apple.com/wwdc20/10119 and https://developer.apple.com/wwdc20/10040. Once you are done with it you can view other links under the videos.

Confusion about NavigationSplitView There seem to be 2 ways: Option 1: WWDC video (https://developer.apple.com/wwdc22/10054) uses NavigationLink for NavigationSplitView Option 2: Documentation (https://developer.apple.com/documentation/swiftui/navigationsplitview) they don't use NavigationLink Not sure what is the correct approach, using NavigationLink seems to require navigationDestination but that doesn't sit well with NavigationSplitView as the destination view is specified part of the detail closure and repeating the code would be redundant. Following the documentation (without NavigationLink): Following https://developer.apple.com/documentation/swiftui/navigationsplitview documentation things seem to work ok, there is only one warning thrown (as opposed to 3 before): Update NavigationAuthority bound selection tried to update multiple times per frame. The other 2 warnings about navigationDestination and Focus are not thrown I really wish someone from the Apple team could clarify on this, please.

I think there is a typo .weigh after Image(systemName: "rectangle.portrait.and.arrow.right.fill")

The key is to use a Label for it to work on macOS example: Text("aaa") .swipeActions { Button { //Do something } label: { Label("Delete", systemImage: "trash") //Use a label }

My scenario I had merged a lot of changes from a branch (pull request) I had also made changes to the swift package Problem Export archive for app-store distribution Command exited with non-zero exit-code: 70 Solution / Workaround Cleared DerivedData Cloned the project in a disk location

I am getting the "Could not load Xcode Cloud data" on macOS Monterey (12.5 Beta (21G5037d))

You could add .frame modifier to set any height

I am not sure I understand your question correctly, contextMenu could be added to any custom view struct ContentView: View { var body: some View { Text("Hello, world!") .padding() .contextMenu { Button("aaa") {} } } }

Use a ZStack instead of overlay ZStack { Text("Hello, world!") .padding() Rectangle() .fill(.red) }

Remove Selection Can you set selectedRecipe = nil, that should remove any selection of the recipe. Selection of recipe is driven by the state variable selectedRecipe so depending on the value different recipes Reference: https://developer.apple.com/documentation/swiftui/list

I have filed a feedback FB9793368 DTS has confirmed this is a bug, hope it gets fixed, fingers crossed

I think What's new in SwiftUI talk explains this https://developer.apple.com/wwdc22/10052 (11:39) https://developer.apple.com/documentation/swiftui/radialgradient/presentationdetents(_:)

Thanks a lot Quinn!!! The following don't seem to be working for me: Upvoting an answer, shows as upvoted but when I signout the upvote doesn't show as upvoted Email notification as mentioned above don't work even selected Also it would be nice to have email notifications checked by default for the question you ask, as most people would expect that by default. IMHO improving the website can directly improve the engagement with in the developers as more people will use the forums and more questions would get asked and answered.