Releases: 3lvis/Sync
Releases · 3lvis/Sync
Sync — 1.6.6
Updated to DATAStack 5.0.0
Release notes from DATAStack here:
- Refactored all the things to have better error handling and better code coverage
- Added a new method to create a background context, super useful when doing saves with NSOperations
public func newBackgroundContext() -> NSManagedObjectContext
BREAKING CHANGE
- Removed the need to call
persistWithCompletion
orpersist
, you just need to save your used context and magic will happen
// Just kill this babies, they are no longer needed
dataStack.persist {error in
}
dataStack.persistWithCompletion {
}
- Now
drop()
throws, before it was hiding the error message but now you can deal with that. If you're an Objective-C user this will no work for you, useforceDrop()
instead
Before:
dataStack.drop()
After:
try dataStack.drop()
Sync — 1.6.5
- Fix bug where many to many relationship didn't cleared contents of relationship when sending empty list of children. More information on: #202
Thanks to @xTheRamon for reporting this issue 👏
Sync — 1.6.4
- Updated DATAStack to 4.2.4
Sync — 1.6.3
- Converted forced unwrapped optionals into fatalErrors for better crash reporting
Sync — 1.6.2
Updated NSManagedObject-HYPPropertyMapper — 3.6.0, which now includes support for transformable types. Make sure to check the relevant pull request for more information.
@AlexKel kicks ass.
Sync — 1.6.1
- Updated DATAStack containing fix for TestCheck not working fine in Xcode 7.3
Thanks @wh33ler, you rock!
Previously in 1.6.0
AUTOMATIC SUPPORT FOR CAMELCASE MAPPINGS!
🎉 🎉 OMG OMG OMG 🎉 🎉
This comes thanks to @wainglaister who added this feature to NSManagedObject-HYPPropertyMapper. Fuck yeah!
Sync — 1.6.0
AUTOMATIC SUPPORT FOR CAMELCASE MAPPINGS!
🎉 🎉 OMG OMG OMG 🎉 🎉
This comes thanks to @wainglaister who added this feature to NSManagedObject-HYPPropertyMapper. Fuck yeah!
Sync — 1.5.4
- Updated NSManagedObject-HYPPropertyMapper dependecy to
3.4.3
Sync — 1.5.3
- Updated for Swift 2.2
Sync — 1.5.2
- Fixed an issue with using an entity that has multiple many-to-many relationships.
For example:
This comes thanks to the fantastic @wainglaister in #179. 👏 👏 👏 👏 👏 👏