Sync

• Updated to Xcode 12

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

• Update to Xcode 11.5

• Support for Swift 5 & Xcode 10.2

• 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)

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

• Add support for deciseconds https://github.com/3lvis/Sync/pull/536
• Add support for centiseconds https://github.com/3lvis/Sync/pull/533

• 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)

• 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: https://github.com/3lvis/Sync/issues/497

• Fixes an issue with forcing all requests to work in "isTesting" mode, meaning synchronously. https://github.com/3lvis/Sync/pull/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). https://github.com/3lvis/Sync/commit/d970043d47b92b8be01d38b499ba7df7e1e2368c

FileManager.sqliteDirectoryURL

• Updated to Xcode 9.4.1
• Improve handling of microseconds and miliseconds (https://github.com/3lvis/Sync/commit/8ee867884196a5dd38e2c512ff2e08639af01703)
• Support for new UUID and URI data types (https://github.com/3lvis/Sync/pull/511)

• Fixes export not working for nested JSON objects (https://github.com/3lvis/Sync/pull/485)

• Update to Xcode 9.3

• Fixed an issue with many-to-many relationships with custom IDs. https://github.com/3lvis/Sync/pull/477

• Annotates the background context with a name to avoid calling it when other contexts are saved https://github.com/3lvis/Sync/pull/473 https://github.com/3lvis/DATAStack/issues/111

• Adds support for the new UUID (both insertion and export) https://github.com/3lvis/Sync/pull/472

• Fixes a crash in to-many relationships #467

• Fixes an issue with duplicated primary keys #471 (@batjo)

Before the following JSON would create 6 body entries, now is only 3.

[{
    "id":0,
    "title":"story 1",
    "comments":[{
        "body":"comment 1"
      },{
        "body":"comment 2"
      },{
        "body":"comment 3"
      }]
  },
  {
    "id":1,
    "title":"story 2",
    "comments":[{
        "body":"comment 1"
      },{
        "body":"comment 2"
      },{
        "body":"comment 3"
      }]
  }]

• Fixes an issue where sending empty or null wouldn't remove the element #459

• Added a code of conduct #468

• 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.

• Fixes an issue where if you had several stores the completion block would be triggered when every store was dropped.

https://github.com/3lvis/Sync/pull/439

• #366: Fix operation is never marked as finished (#435)

• Improved Objective-C support thanks to @alejouribesanchez

Xcode 9 and Swift 4 support.

• Fix issue where persistent store wouldn't get recreated after dropping database https://github.com/3lvis/Sync/issues/398