Swift Sequence Contents in LLDB

If you need lldb to give you more information about objects in a Swift Sequence structure other than their address in memory, here's a useful tip:

Swift 3: Unit Testing Core Data With Generics

So I'm starting a new iOS app and using this opportunity to learn Swift. This app uses Core Data so I am going to be running unit tests to ensure that my data source class performs well. As anyone who has ever unit tested Core Data functionality knows, verifying the contents of the persistent store can get mind-bogglingly boiler-plate.

guard vs. if-let (Or: The Cost of Pyramids of Doom)

Recently read a post by Natasha The Robot after Apple introduced the 'guard' keyword in Swift 2.0. The article itself has good examples of code implemented with if-let vs guard, but the more compelling part of the post were in the comments themselves.

Swift At Last

After a nearly two year hiatus I've decided to reactivate my dev blog. Mainly spurred by my initiative to finally get off my Objective-C soap box and learn Swift. I've done the introductory tutorials from Ray Wenderlich to learn the basics of Swift. Downloaded the Swift iBook, yadda, yadda, yadda. 

You've Come A Long Way, Baby

Spendu, version 1.0.0, is finally out! Apple approved my first app for sale in the App Store a couple of days ago and it feels awesome to finally realize one of my personal goals. I thought it would be fun take a look back on Spendu then and now just to see how far it's come.
 

Core Data Custom Migration, Part 3: Initiating Migration

My previous post was the second part in a three part series documenting my attempt at using a custom migration from one Core Data model version to another. I implemented custom NSEntityMigrationPolicy code to create the destination entities and to convert the currency values typed as double into values typed as decimal.

This post will show how to initiate default migration using the mapping model and custom migration policy code from the last posting.
 

Core Data Custom Migration, Part 2: Custom Migration Code

In my last post, I wrote about the change I found myself needing to make in order to properly represent currency value information in Core Data using the built-in decimal type as opposed to the double type. I described the process involved in versioning the Core Data model, adding a mapping model from the previous version to the new version, and specifying custom NSEntityMigrationPolicy classes for each entity that needed to be mapped to the new version.

In this post we'll see about implementing the NSEntityMigrationPolicy subclass code for converting existing currency double values into decimal values.