SwiftUI中CoreData实体如何实现属性自动求和并存储？

有两种可靠的实现方式，分别从模型层自动同步和UI层实时更新入手，均可满足需求：

方式一：模型层自动计算并存储（推荐） #

借助CoreData的属性监听机制，当任意关卡分数变化时自动计算总分并更新scoretotal属性，同时确保UI实时刷新。

修改Players模型扩展 #

extension Players {

    @nonobjc public class func fetchRequest() -> NSFetchRequest<Players> {
        return NSFetchRequest<Players>(entityName: "Players")
    }

    @NSManaged public var name: String?
    @NSManaged public var scorelevel1: Int16
    @NSManaged public var scorelevel2: Int16
    @NSManaged public var scorelevel3: Int16
    @NSManaged public var scoretotal: Int16
    
    public var wrappedName: String {
        name ?? "player unknown"
    }
    
    // 计算并更新总分
    private func updateTotalScore() {
        scoretotal = scorelevel1 + scorelevel2 + scorelevel3
        // 可选：立即持久化到CoreData，也可在合适时机统一保存上下文
        do {
            try managedObjectContext?.save()
        } catch {
            let nsError = error as NSError
            fatalError("保存失败：\(nsError), \(nsError.userInfo)")
        }
    }
    
    // 重写setValue方法监听分数属性变化
    override public func setValue(_ value: Any?, forKey key: String) {
        super.setValue(value, forKey: key)
        if key == "scorelevel1" || key == "scorelevel2" || key == "scorelevel3" {
            updateTotalScore()
        }
    }
}

extension Players : Identifiable { }

更新PlayerView显示总分 #

在VStack末尾添加总分展示：

struct PlayerView: View {

    @ObservedObject var player: Players
    @Environment(\.managedObjectContext) var moc

    var body: some View {
        VStack {
            Text(player.wrappedName)
            TextField("关卡1分数", value: $player.scorelevel1, formatter: NumberFormatter())
                .textFieldStyle(.roundedBorder)
            TextField("关卡2分数", value: $player.scorelevel2, formatter: NumberFormatter())
                .textFieldStyle(.roundedBorder)
            TextField("关卡3分数", value: $player.scorelevel3, formatter: NumberFormatter())
                .textFieldStyle(.roundedBorder)
            // 展示计算后的总分
            Text("总分：\(player.scoretotal)")
                .font(.headline)
                .foregroundColor(.blue)
        }
        .padding()
    }
}

方式二：UI层实时计算并同步到模型 #

在PlayerView中监听每个分数输入框的变化，实时计算总和并同步到CoreData的scoretotal属性，适合新手快速理解逻辑。

修改PlayerView代码 #

struct PlayerView: View {

    @ObservedObject var player: Players
    @Environment(\.managedObjectContext) var moc
    
    // 实时计算总分
    private var totalScore: Int16 {
        player.scorelevel1 + player.scorelevel2 + player.scorelevel3
    }
    
    // 配置整数输入限制（可选，避免用户输入小数）
    private let numberFormatter: NumberFormatter = {
        let formatter = NumberFormatter()
        formatter.numberStyle = .decimal
        formatter.allowsFloats = false
        return formatter
    }()

    var body: some View {
        VStack {
            Text(player.wrappedName)
            TextField("关卡1分数", value: $player.scorelevel1, formatter: numberFormatter)
                .textFieldStyle(.roundedBorder)
                .onChange(of: player.scorelevel1) { _ in
                    syncTotalScore()
                }
            TextField("关卡2分数", value: $player.scorelevel2, formatter: numberFormatter)
                .textFieldStyle(.roundedBorder)
                .onChange(of: player.scorelevel2) { _ in
                    syncTotalScore()
                }
            TextField("关卡3分数", value: $player.scorelevel3, formatter: numberFormatter)
                .textFieldStyle(.roundedBorder)
                .onChange(of: player.scorelevel3) { _ in
                    syncTotalScore()
                }
            // 展示实时总分
            Text("总分：\(totalScore)")
                .font(.headline)
                .foregroundColor(.blue)
        }
        .padding()
    }
    
    // 将计算后的总分同步到CoreData
    private func syncTotalScore() {
        player.scoretotal = totalScore
        do {
            try moc.save()
        } catch {
            print("保存上下文失败：\(error)")
        }
    }
}

额外提示 #

• 如果不需要每次修改都立即保存CoreData，可以移除save()调用，改为在用户完成所有输入后统一触发保存（比如添加一个保存按钮）。
• 两种方式都能保证scoretotal属性与三个关卡分数保持同步，模型层方式更符合CoreData的设计原则，适合复杂场景；UI层方式更直观，适合简单场景。

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