在macOS的NavigationSplitView中选中新增SwiftData对象的更优雅方案？

方案1：插入后直接设置选中（利用SwiftData对象引用特性） #

SwiftData的对象是引用类型，即使@Query的items数组还未完成更新，直接将新创建的对象赋值给selectedItem，后续items同步后，List会自动识别该对象并完成高亮选中。如果存在同步延迟，可手动调用save()加速上下文状态同步：

struct ContentView: View {
    @Environment(\.modelContext) private var modelContext
    @Query private var items: [Item]
    @State private var selectedItem: Item?
    
    var body: some View {
        NavigationSplitView {
            List(selection: $selectedItem) {
                ForEach(items) { item in
                    NavigationLink(value: item, label: { Text(verbatim: item.name) })
                }
            }
            .navigationSplitViewColumnWidth(min: 180, ideal: 200)
            .toolbar {
                Button("Add", systemImage: "plus", action: addItem)
            }
        } detail: {
            DetailView(item: selectedItem)
        }
        .task {
            selectedItem = items.first
        }
    }
    
    private func addItem() {
        let newItem = Item()
        withAnimation {
            modelContext.insert(newItem)
            try? modelContext.save() // 手动触发保存，加快上下文同步
            selectedItem = newItem // 直接赋值，利用引用一致性
        }
    }
}

方案2：监听items数组更新，自动选中最新元素 #

无需额外暂存对象，直接在items数组变化时选中最后一个元素（即刚添加的对象），适合需要确保选中最新项的场景：

struct ContentView: View {
    @Environment(\.modelContext) private var modelContext
    @Query private var items: [Item]
    @State private var selectedItem: Item?
    
    var body: some View {
        NavigationSplitView {
            List(selection: $selectedItem) {
                ForEach(items) { item in
                    NavigationLink(value: item, label: { Text(verbatim: item.name) })
                }
            }
            .navigationSplitViewColumnWidth(min: 180, ideal: 200)
            .toolbar {
                Button("Add", systemImage: "plus", action: addItem)
            }
        } detail: {
            DetailView(item: selectedItem)
        }
        .task {
            selectedItem = items.first
        }
        .onChange(of: items) { _, newItems in
            selectedItem = newItems.last // 直接选中最新添加的元素
        }
    }
    
    private func addItem() {
        let newItem = Item()
        withAnimation {
            modelContext.insert(newItem)
        }
    }
}

方案3：用ViewModel封装状态逻辑 #

如果需要更复杂的状态管理，可封装ViewModel，利用SwiftData上下文的变化通知来更新选中状态，实现视图与数据逻辑解耦：

class ItemViewModel: ObservableObject {
    @Published var selectedItem: Item?
    private var cancellables = Set<AnyCancellable>()
    
    init(modelContext: ModelContext, initialItems: [Item]) {
        selectedItem = initialItems.first
        // 监听上下文对象变化
        modelContext.objectWillChange
            .sink { [weak self] _ in
                guard let items = try? modelContext.fetch(FetchDescriptor<Item>()) else { return }
                self?.selectedItem = items.last
            }
            .store(in: &cancellables)
    }
}

struct ContentView: View {
    @Environment(\.modelContext) private var modelContext
    @Query private var items: [Item]
    @StateObject private var viewModel: ItemViewModel
    
    init() {
        let context = ModelContext(Item.schema)
        _viewModel = StateObject(wrappedValue: ItemViewModel(modelContext: context, initialItems: []))
    }
    
    var body: some View {
        NavigationSplitView {
            List(selection: $viewModel.selectedItem) {
                ForEach(items) { item in
                    NavigationLink(value: item, label: { Text(verbatim: item.name) })
                }
            }
            .navigationSplitViewColumnWidth(min: 180, ideal: 200)
            .toolbar {
                Button("Add", systemImage: "plus", action: addItem)
            }
        } detail: {
            DetailView(item: viewModel.selectedItem)
        }
        .task {
            viewModel.selectedItem = items.first
        }
    }
    
    private func addItem() {
        let newItem = Item()
        withAnimation {
            modelContext.insert(newItem)
        }
    }
}

方案对比 #

• 方案1最简洁，依托SwiftData引用特性，适合多数常规场景；
• 方案2无需额外状态变量，逻辑直接，适合固定选中最新项的需求；
• 方案3适合复杂状态管理场景，实现视图与数据逻辑解耦。

内容的提问来源于stack exchange，提问作者Amar Sagoo