Previously, I sorted my FetchResult in a TableView like this:
@FetchRequest(
sortDescriptors: [SortDescriptor(\.rechnungsDatum, order: .forward)],
predicate: NSPredicate(format: "betragEingang == nil OR betragEingang == 0")
)
private var verguetungsantraege: FetchedResults<VerguetungsAntraege>
...
body
...
Table(of:VerguetungsAntraege.self, sortOrder: $verguetungsantraege.sortDescriptors) {
TableColumn("date", value:\.rechnungsDatum) { item in
Text(Formatters.dateFormatter.string(from: item.rechnungsDatum ?? Date()) )
}
.width(120)
TableColumn("rechNrKurz", value:\.rechnungsNummer) { item in
Text(item.rechnungsNummer ?? "")
}
.width(120)
TableColumn("betrag", value:\.totalSum ) {
Text(Formatters.currencyFormatter.string(from: $0.totalSum as NSNumber) ?? "kein Wert")
}
.width(120)
TableColumn("klient") {
Text(db.getKlientNameByUUID(id: $0.klient ?? UUID(), moc: moc))
}
} rows: {
ForEach(Array(verguetungsantraege)) { antrag in
TableRow(antrag)
}
}
There seem to be changes here in Xcode 26. In any case, I always get the error message in each line with TableColumn("title", value: \.sortingField)
Ambiguous use of 'init(_:value:content:)'
Does anyone have any idea what's changed? Unfortunately, the documentation doesn't provide any information.
