A lightweight Core Data stack with efficient importing and exporting on the side.
Vokoder is available through CocoaPods. To install it, simply add the following line to your Podfile:
pod "Vokoder"
If you intend to use Vokoder in Swift, use the Swift subspec instead:
pod "Vokoder/Swift"
Vokoder requires iOS 7, tvOS 9, or macOS 10.9. The Swift extensions require Swift 3 and Xcode 8.
The bulk of the functionality is in the Core subspec. If you aren't using any of the data sources, you can just include the Core subspec.
Data sources to facilitate backing various kinds of views with data from Core Data are in the DataSources subspec, which is further broken down into:
FetchedResultscontains a basic data source based on a fetched results controller, intended to be used with aUITableView.PagingFetchedResultsis based onFetchedResultsbut supports paged loading.Collectionis based onFetchedResults, but intended for use with aUICollectionView.
The optional Swift subspec includes some Swift extensions for strong typing and cleaner syntax. It is recommended to use this subspec if you intend to use Vokoder in Swift. This subspec includes all of the other subspecs.
Macros to help create managed object property maps for importing and exporting are included in the MapperMacros subspec. This subspec is included by default, but excluded from the Swift subspec since the macros are only usable from Objective-C code.
// Omit the .xcdatamodeld extension on the model file name
// Save to disk
[[VOKCoreDataManager sharedInstance] setResource:@"VOKCoreDataModel"
database:@"VOKCoreDataModel.sqlite"];
// Or, create an in-memory store:
[[VOKCoreDataManager sharedInstance] setResource:@"VOKCoreDataModel"
database:nil];Vokoder offers a lightweight mapper for importing Foundation objects into Core Data. Arrays of dictionaries can be imported with ease once maps are set up. If no maps are provided Vokoder will use its default maps. The default maps assume that foreign keys have the same names as your Core Data attributes. It will make its best effort to identify dates and numbers.
Setting up your own maps is recommended. Macros are provided to make it fun and easy. Below is an example of setting up a mapper for a managed object subclass VOKPerson. Mappers are not persisted between app launches, so be sure to setup your maps every time your application starts. Note that this example makes use of the VOKKeyForInstanceOf macro from VOKUtilities/VOKKeyPathHelper, which is a dependency for Vokoder.
// A date formatter will enable Vokoder to turn strings into NSDates
NSDateFormatter *dateFormatter = [NSDateFormatter someCustomDateFormatter];
// A number formatter will do the same, turning strings into NSNumbers
NSNumberFormatter *numberFormatter = [NSNumberFormatter new];
NSArray *maps = @[
VOKMapForeignToLocalClassProperty(@"ticket_number", VOKPerson, ticketNumber), //the first argument is the foreign key,
VOKMapForeignToLocalClassProperty(@"first_name", VOKPerson, firstName), //second argument is the class, and then local property
VOKMapForeignToLocalClassProperty(@"last_name", VOKPerson, lastName),
VOKMapForeignToLocalClassProperty(@"ss_num", VOKPerson, socialSecurityNumber),
[VOKManagedObjectMap mapWithForeignKeyPath:@"salary"
coreDataKey:VOKKeyForInstanceOf(VOKPerson, salary)
numberFormatter:numberFormatter],
[VOKManagedObjectMap mapWithForeignKeyPath:@"dob"
coreDataKey:VOKKeyForInstanceOf(VOKPerson, dateOfBirth)
dateFormatter:dateFormatter],
];
// The VOKKeyForInstanceOf(...) macro will prevent you from specifying a property that does not exist on a specific class.
// The unique key is an NSString to uniquely identify local entities. If nil, each import can create duplicate objects.
VOKManagedObjectMapper *mapper = [VOKManagedObjectMapper mapperWithUniqueKey:VOKKeyForInstanceOf(VOKPerson, ticketNumber)
andMaps:maps];
// By default, missing parameters and null parameters in the import data will nil out an attribute's value.
// With ignoreNullValueOverwrites set to YES, the maps will leave existing attributes alone unless new data is provided.
mapper.ignoreNullValueOverwrites = YES;
// By default, Vokoder will complain about every single parameter that can't be set.
// With ignoreOptionalNullValues set to YES, Vokoder will not warn about mismatched classes or null/nil values.
mapper.ignoreOptionalNullValues = YES;
// Set the mapper and Vokoder will handle the rest.
[[VOKCoreDataManager sharedInstance] setObjectMapper:mapper
forClass:[VOKPerson class]];Once the mapper is set Vokoder can turn Foundation objects in to managed objects and then back again to Foundation objects.
Vokoder includes the VOKMappableModel protocol, which gives a structure for a model class to specify how it should be mapped. Any classes that declare themselves to conform to VOKMappableModel will automatically have mappers created based on the protocol methods and registered with the shared instance of VOKCoreDataManager.
The VOKMappableModel protocol requires implementing + (NSString *)uniqueKey and + (NSArray *)coreDataMaps, which should return the two parameters passed to [VOKManagedObjectMapper mapperWithUniqueKey:andMaps:] in the example in the section above. Optionally, + (BOOL)ignoreNullValueOverwrites, + (BOOL)ignoreOptionalNullValues, and + (VOKPostImportBlock)importCompletionBlock can each be implemented to set the ignore values on the mapper or to set a post-import block.
The mapper constructed in the example in the section above could be included in SomeManagedObjectSubclass by making it conform to VOKMappableModel.
@interface SomeManagedObjectSubclass : NSManagedObject <VOKMappableModel>
// …properties and such
@end
@implementation SomeManagedObjectSubclass
// …other methods and such
#pragma mark - VOKMappableModel
+ (NSArray *)coreDataMaps
{
// A date formatter will enable Vokoder to turn strings into NSDates
NSDateFormatter *dateFormatter = [NSDateFormatter someCustomDateFormatter];
// A number formatter will do the same, turning strings into NSNumbers
NSNumberFormatter *numberFormatter = [NSNumberFormatter new];
return = @[
VOKMapForeignToLocalForSelf(@"ticket_number", ticketNumber),
VOKMapForeignToLocalForSelf(@"first_name", firstName),
VOKMapForeignToLocalForSelf(@"last_name", lastName),
VOKMapForeignToLocalForSelf(@"ss_num", socialSecurityNumber),
[VOKManagedObjectMap mapWithForeignKeyPath:@"salary"
coreDataKey:VOKKeyForSelf(salary)
numberFormatter:numberFormatter],
[VOKManagedObjectMap mapWithForeignKeyPath:@"dob"
coreDataKey:VOKKeyForSelf(dateOfBirth)
dateFormatter:dateFormatter],
];
}
+ (NSString *)uniqueKey
{
// The VOKKeyForSelf(...) macro will prevent you from specifying a property that does not exist on the current class.
// The unique key is an NSString to uniquely identify local entities. If nil each import can create duplicate objects.
return VOKKeyForSelf(ticketNumber);
}
+ (BOOL)ignoreNullValueOverwrites
{
// By default, missing parameters and null parameters in the import data will nil out an attribute's value.
// With ignoreNullValueOverwrites set to YES, the maps will leave set attributes alone unless new data is provided.
return YES;
}
+ (BOOL)ignoreOptionalNullValues
{
// By default Vokoder will complain about every single parameter that can't be set
// With ignoreOptionalNullValues set to YES Vokoder will not warn about mismatched classes or null/nil values
return YES;
}
…
@endVokoder offers many ways to get data into Core Data. The simplest and most approachable interface is offered through the VOKManagedObjectAdditions category. Given an array of dictionaries, Vokoder will create or update managed objects on a temporary context and then safely return managed objects from the main context through a completion block on the main queue.
[SomeManagedObjectSubclass vok_addWithArrayInBackground:importArray
completion:^(NSArray *arrayOfManagedObjects) {
// This completion block runs on the main queue
SomeManagedObjectSubclass *obj = arrayOfManagedObjects.firstObject;
}];
For more control over background operations, the VOKCoreDataManager class offers more generic methods. Vokoder will handle queues and provide a temporary context without automatically importing or returning anything.
+ (void)writeToTemporaryContext:(VOKWriteBlock)writeBlock completion:(void (^)(void))completion;Finally, for those that want full control, you can make your own temporary contexts that each have their own serial background queue. As long as you use a temporary context for background operations, Vokoder will let you go your own way.
NSManagedObjectContext *backgroundContext = [[VOKCoreDataManager sharedInstance] temporaryContext];
[backgroundContext performBlock:^{
SomeManagedObjectSubclass *thing = [SomeManagedObjectSubclass vok_newInstanceWithContext:backgroundContext];
thing.someArbitrayAttribute = @"hello";
[[VOKCoreDataManager sharedInstance] saveAndMergeWithMainContext:backgroundContext];
}];NOTE: Temporary contexts created manually or vended through the convenience background methods are child contexts of the main context.
VOKPerson *person = [VOKPerson vok_newInstance];
person.firstName = @"Rohan";
person.lastName = @"Panchal";
[[VOKCoreDataManager sharedInstance] saveMainContextAndWait];Like the example above, this one makes use of the VOKKeyForInstanceOf macro from VOKUtilities/VOKKeyPathHelper for the keys in these calls to ensure that typos like @"lsatName" don't occur.
NSPredicate *smithsPredicate = [NSPredicate predicateWithFormat:@"%K == %@", VOKKeyForInstanceOf(VOKPerson, lastName), @"Smith"];
// Passing `nil` for any managed object context parameter uses the main context
NSArray *allSmiths = [VOKPerson vok_fetchAllForPredicate:smithsPredicate forManagedObjectContext:nil];NSPredicate *smithsPredicate = [NSPredicate predicateWithFormat:@"%K == %@", VOKKeyForInstanceOf(VOKPerson, lastName), @"Smith"];
NSArray *sortedSmiths = [VOKPerson vok_fetchAllForPredicate:smithsPredicate
sortedByKey:VOKKeyForInstanceOf(VOKPerson, firstName)
ascending:YES
forManagedObjectContext:nil];NSPredicate *personPredicate = [NSPredicate predicateWithFormat:@"%K == %@", VOKKeyForInstanceOf(VOKPerson, ticketNumber), @"A14"];
VOKPerson *person = [VOKPerson vok_fetchForPredicate:personPredicate
forManagedObjectContext:nil];
[[VOKCoreDataManager sharedInstance] deleteObject:person];
[[VOKCoreDataManager sharedInstance] saveMainContextAndWait];//Saves the main context synchronously
[[VOKCoreDataManager sharedInstance] saveMainContextAndWait];
//Saves the main context asynchronously
[[VOKCoreDataManager sharedInstance] saveMainContext];
//Save a temp context and merge changes to the main context asynchronously
[[VOKCoreDataManager sharedInstance] saveAndMergeWithMainContext:tempContext];
//Save a temp context and merge changes to the main context synchronously
[[VOKCoreDataManager sharedInstance] saveAndMergeWithMainContextAndWait:tempContext];NOTE: There is a private context that asynchronously saves changes to the persistent store when any of these methods are called. The main context is a child of this "root" context. This should not pose a problem if you are using the main context and temporary contexts. If you have created a context that is not a descendent of the main context, be aware of this.
For Swift 2: use Vokoder versions 2.x and 3.x. This support is being maintained in the swift2 branch.
For Swift 3: use Vokoder versions 4.x. or 5.x.
For Swift 4: Use Vokoder Versions 6.x.
For Swift 4.2: Use Vokoder Versions 7.x.
For Swift 5: Use Vokoder Versions 8.x.
Vokoder is available under the MIT license. See the LICENSE file for more info.