Sync — 6.5.0

• Updated to Xcode 12

Sync — 6.0.3

• Rename Result type to avoid conflicts with Swift 5's Result type #578

Sync — 6.0.2

• Update to Xcode 11.5

Sync — 6.0.0

• Support for Swift 5 & Xcode 10.2

Sync — 5.2.1

• Support for Swift 4.2 and Xcode 10 (@philip-zhan)
• Improved the way nested relationships work (@joeboyscout04)
• Improved support for parsing dates (@Kemmey)
• Added an extra parameter to public class func changes... (@petkrein)

5.1.0 (Xcode 10 and Swift 4.2)

• Support for Xcode 10 and Swift 4.2
• API stays the same

Sync — 5.0.1

• Add support for deciseconds #536
• Add support for centiseconds #533

Sync — 5.0.0

• Added support for extended operation options #433

Before you could set insert, update and delete operations and that worked for both parents and children, now you have more control and can also decide if children follow these rules using insertRelationships, updateRelationships and deleteRelationships.

⚠️ Breaking change ⚠️

If you were using the .insert, .update, or .delete options now you'll also need to set .insertRelationships, .updateRelationships or . deleteRelationships based on what are your needs.

If you weren't using OperationOptions then you won't need to do anything since it will default to .all

What's operation options?

It's a feature that allows you to have more control over what happens when using Sync, you can then tell sync to only do inserts and updates, or only do inserts and deletes and so on.

Looks like this:

dataStack.sync(updated, inEntityNamed: "User", operations: [.insert, .update, .delete, .deleteRelationships], completion: nil)

Sync — 4.3.0

• Rollback extended sync operations

Extended operations was a breaking change, it didn't break the compilation but it broke functionality, this release aims for fix that, I'll reintroduce the feature in a separate major release: #497

Sync — 4.2.1

• Fixes an issue with forcing all requests to work in "isTesting" mode, meaning synchronously. #522

• Introduced an extension to FileManager to get the directory URL where the sqlite file is stored. Since it can be different when running on device or in unit tests (because of sandboxing reasons we switch between caches folder and directory when needed). d970043

FileManager.sqliteDirectoryURL