如何在SwiftUI的NavigationSplitView中优雅预选动态项？

在macOS应用中使用NavigationSplitView构建界面，主视图代码如下：

struct NavigationView: View {
    
    @State private var selectedApplication: Application?
    
    var body: some View {
        NavigationSplitView {
            ApplicationsView(selectedApplication: $selectedApplication)
        } detail: {
            Text(selectedApplication?.name ?? "Nothing selected")
        }
    }
}

侧边栏由ApplicationsView实现，代码如下：

struct ApplicationsView: View {
    
    @FetchRequest(fetchRequest: Application.all()) private var applications
    @Binding var selectedApplication: Application?
    
    var body: some View {
        List(applications, selection: $selectedApplication) { application in
            NavigationLink(value: application) {
                Text(application.name)
            }
        }
        
        // 可行但不够优雅的实现，需要延迟执行
        .onReceive(applications.publisher) { _ in
            DispatchQueue.main.asyncAfter(deadline: .now() + 0.01) {
                if selectedApplication == nil {
                    selectedApplication = applications.first
                }
            }
        }

        // 无效，因为数据加载完成前就执行了
        .onAppear {
            selectedApplication = applications.first
        }
    }
}

当前通过onReceive加延迟的方式默认选中首个Application项，但实现复杂且不优雅，希望找到更优的实现方式。

方案1：用onChange监听applications数组变化 #

直接监听applications的更新，当Core Data数据加载完成、数组从空变为有内容时，自动设置默认选中项，同时保留用户已有的选择：

struct ApplicationsView: View {
    
    @FetchRequest(fetchRequest: Application.all()) private var applications
    @Binding var selectedApplication: Application?
    
    var body: some View {
        List(applications, selection: $selectedApplication) { application in
            NavigationLink(value: application) {
                Text(application.name)
            }
        }
        .onChange(of: applications) { newApplications in
            // 仅在未选中任何项时设置默认值
            if selectedApplication == nil, let firstApp = newApplications.first {
                selectedApplication = firstApp
            }
        }
    }
}

这个方案替代了onReceive+延迟的写法，onChange专门用于监听值的变化，逻辑清晰且不需要依赖异步延迟，完全适配Core Data的异步加载特性。

方案2：将默认选中逻辑移至父视图 #

把选中逻辑集中到NavigationView中，让侧边栏视图更专注于列表展示：

struct NavigationView: View {
    
    @State private var selectedApplication: Application?
    @FetchRequest(fetchRequest: Application.all()) private var applications
    
    var body: some View {
        NavigationSplitView {
            ApplicationsView(selectedApplication: $selectedApplication)
        } detail: {
            Text(selectedApplication?.name ?? "Nothing selected")
        }
        .onChange(of: applications) { newApplications in
            if selectedApplication == nil, let firstApp = newApplications.first {
                selectedApplication = firstApp
            }
        }
    }
}

struct ApplicationsView: View {
    @Binding var selectedApplication: Application?
    @FetchRequest(fetchRequest: Application.all()) private var applications
    
    var body: some View {
        List(applications, selection: $selectedApplication) { application in
            NavigationLink(value: application) {
                Text(application.name)
            }
        }
    }
}

这种方式适合需要在父视图统一管理状态的场景，避免子视图承担过多逻辑。

方案3：结合视图初始化与onChange #

如果希望在视图初始化时就尝试设置默认值，同时处理异步加载的情况，可以在init中补充判断，再配合onChange保障最终效果：

struct ApplicationsView: View {
    
    @FetchRequest(fetchRequest: Application.all()) private var applications
    @Binding var selectedApplication: Application?
    
    init(selectedApplication: Binding<Application?>) {
        self._selectedApplication = selectedApplication
        self._applications = FetchRequest(fetchRequest: Application.all())
        // 初始化时尝试设置（仅当数据已加载完成时生效）
        if let firstApp = applications.wrappedValue.first {
            self._selectedApplication.wrappedValue = firstApp
        }
    }
    
    var body: some View {
        List(applications, selection: $selectedApplication) { application in
            NavigationLink(value: application) {
                Text(application.name)
            }
        }
        .onChange(of: applications) { newApplications in
            if selectedApplication == nil, let firstApp = newApplications.first {
                selectedApplication = firstApp
            }
        }
    }
}

这个方案兼顾了同步初始化和异步加载两种场景，但核心仍然依赖onChange处理异步数据就绪的情况。

内容的提问来源于stack exchange，提问作者Niels Mouthaan