Making Item optional fixes the problem: var item: Item?
quaternionboy
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
From
Barcelona, Spain
Post
Replies
Boosts
Views
Activity
workaround
@Model
final class Item {
var name: String
var id: UUID
@Relationship(deleteRule:.cascade, inverse: \Entry.item) var entries: [Entry]
init(name: String) {
self.name = name
self.id = UUID()
entries = []
}
}
extension Item {
private var _entries: [Entry]? {
return try? self.context?.fetch(FetchDescriptor<Entry>(predicate:#Predicate<Entry>{
$0.item.id == id},sortBy: [SortDescriptor(\Entry.date, order: .forward)]))
}
}
extension Item {
func checkingDate()->Date?{
let _ = _entries
//...
return Date()
}
}
But is really awkward not allowed directly to access the collection property inside one entity...
https://github.com/quaternionboy/LifeKPIs-SwiftData-Data-Model/tree/Profiling-LifeKPIs-Tests
https://github.com/quaternionboy/LifeKPIs-SwiftData-Data-Model
https://github.com/quaternionboy/LifeKPIs-SwiftData-Data-Model