CoreStore | Unleashing the real power of Core Data with the elegance and safety of Swift | iOS library

I'm not sure is it xCode bug or not, however with Swift Package Manager and xCode 11 you have to clearly specify iOS version when use #available check. Not matter if library is targeted for iOS 10+ or not, instead of

I looks like the coreStore is a cool wrapper for core-data and there 'where' method is creating an NSPredicate behinds the scenes. The problem is that you are passing an array of predicates into a method that expects a string.

First turn your array of predicates into a single predicate. use NSCompoundPredicate andPredicateWithSubpredicates (see https://developer.apple.com/documentation/foundation/nscompoundpredicate/1407855-init).

Next, instead of passing it via a string using format, just pass that directly to the where() clause without the word format. I believe that CoreStore accept NSPredicates directly without having to create them from a format.

I think this will work:

I answered your question at CoreStore's github as well.

This would be the general behavior of NSManagedObjects with regards to to-many properties.

First, as you have found out, the inverse relationship is important.

Second, Set is not recommended for unordered @NSManaged properties. Using NSSet is recommended instead. In that note, to-many relationships are treated as immutable, which means you cannot insert objects directly to the NSSet value. There are two ways you can insert values.

1. Assigning a new NSSet directly:

That is because the compiler does not know how to infer the type from your OrderBy argument. Looks like you are using CoreStore, add this as a tag and in the description.

To solve your problem build your query chain like that:

Just replace this:

Don't use basename="..." thoses router are seperate from each other.

https://codesandbox.io/s/suspicious-feather-09ijf

Short no, as John is a Entinity. John needs to be deleted. There is no further action necessary if the relation uses the default nullify rule.

The reason for the crash is that your transaction only lives in your unstoredWorkout() method, so it calles deinit, which resets the context (and deletes all unsaved objects). You have to retain that unsafe transaction somewhere to keep your object alive - such as in the viewcontroller that will eventually save the changes.

But I would rather encourage you to think about that if you really want to do that. You might run into other synchronization issues with various context or other async transactions alive, like when API calls are involved.

That suggestion makes use of the variable name shadowing feature that swift has.

Xcode autocomplete will still show you both "jane", as the other one with the name name also is in the same scope, although can never be used - as it is shadowed. It does not matter what you select there. Because of that reason it is the safest way to handle transaction objects because it prevents you from accidentially using the wrong one.