if you use collections of value types, e.g. [String], SwiftData will save that directly inside a single property too. Right now it’s encoded as binary property list data, which means you can’t use the contents of your array in a predicate.
More: https://www.hackingwithswift.com/quick-start/swiftdata/using-structs-and-enums-in-swiftdata-models
deni2s79
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
Post
Replies
Boosts
Views
Activity
@mark-ger
Was filed as FB14397250
Shows "Feedback not found"
Still having issue in release :(
As a workaround until better solution is found this works:
import Foundation
import SwiftData
@Model
class CaliberData: Identifiable {
var id: UUID = UUID()
var sizeHeights: [SizeObject]
@Transient var sizeHeightsCopy: [SizeObject] // <-here
var featuresABCDIds: [Int]
init(
id: UUID,
sizeHeights: [SizeObject],
featuresABCDIds: [Int],
) {
self.id = id
self.sizeHeights = sizeHeights
self.featuresABCDIds = featuresABCDIds
sizeHeightsCopy = sizeHeights // <-here
}
extension CaliberData: Equatable {
static func == (lhs: CaliberData, rhs: CaliberData) -> Bool {
lhs.featuresABCDIds == rhs.featuresABCDIds
&& lhs.sizeHeightsCopy == rhs.sizeHeightsCopy // <-here
}
}
User should be able to filter CaliberData by specifying size range.
#Predicate {
caliberData in
caliberData.sizeHeights.contains {
sizeObject in
sizeObject.id >= minSizeHeight && sizeObject.id <= maxSizeHeight
}
}
You are right, that Float is actual size value, but had to wrap it into a custom class as a workaround due to some SwiftData limitation regarding using filtering predicates on value (or relationships (or both)).
So using the actual value as 'id' to make it conform to needed Identifiable protocol made sense to save some space.