Changelog History
Page 1
-
v6.5.0 Changes
October 04, 2020- โก๏ธ Updated to Xcode 12
-
v6.0.3 Changes
June 06, 2020- ๐ Rename Result type to avoid conflicts with Swift 5's Result type #578
-
v6.0.2 Changes
June 04, 2020- โก๏ธ Update to Xcode 11.5
-
v6.0.0 Changes
April 16, 2019- ๐ Support for Swift 5 & Xcode 10.2
-
v5.2.1 Changes
January 28, 2019- ๐ 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) -
v5.1.0 Changes
October 06, 2018- ๐ Support for Xcode 10 and Swift 4.2
- API stays the same
-
v5.0.1 Changes
September 17, 2018 -
v5.0.0 Changes
August 23, 2018- โ Added support for extended operation options #433
โก๏ธ Before you could set
insert
,update
anddelete
operations and that worked for both parents and children, now you have more control and can also decide if children follow these rules usinginsertRelationships
,updateRelationships
anddeleteRelationships
.๐ฑ โ ๏ธ 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.0๏ธโฃ 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)
-
v4.3.0 Changes
August 23, 2018- ๐ 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
-
v4.2.1 Changes
July 24, 2018๐ 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). d970043FileManager.sqliteDirectoryURL