Core Data: Fundamentals

Heads up... You've reached locked video content where the transcript will be shown as obfuscated text.

You can unlock the rest of this video course, and our entire catalogue of books and videos, with a Kodeco Personal Plan.

Unlock now

Now that you have a better understanding of the moving parts, let's actually write some code. Download the starter file for this project and let's jump right in. The project contains some of the UI work already done to get you up and running. Build and run the app. You should see nothing remotely close to a rocket launch app. Don't worry, you'll get there. For now, there's a list of placeholder data, along with a button at the bottom to create a new launch. If you tap it, a modal pops up where you can add details about your new launch and hit Save. At the moment, the Save button doesn't do anything and the goal here is to get rid of the mock data, and insert real launches that you persist to the data store. Before you can do that, you need to create the Core Data stack. The first thing you're going to do is add a data model to your project. Right click on the RocketLaunches group and select New File. Scroll down until you find the Core Data section. Select the Data Model and hit Next. Name it RocketLaunches and hit Create. You should see a file added to your project named RocketLaunches.exe datamodeld This file represent the data model in your app. If you click on it, you'll see that it's a visual editor that allows you to define entities. When you learned about managed object models, you learned that Core Data handles creating the underlying data containers for you, and you work through an editor. This is that editor. Don't worry, you'll get to all of this in a second. For now, that's all you need to do. Now that you have the data model, you can create the rest of your stack using the NSPersistentContainer class. If you use the Xcode template that Core Data built in when creating the project, you would get the RocketLaunches.exe datamodeld and NSPersistentContainer class files for free. So let's try to duplicate what you would get from that template. Right click on the Model group and choose New File. And then Swift File and name it Persistence.swift. At the top of the file, after the copyright notice, go ahead and import the CoreData framework so that you can use all its related classes. Create a struct called PersistenceController. Set up two static properties: one for a shared PersistenceController and another for a preview: PersistenceController. Use the shared property to access the context while running the app. The preview context, once populated, will allow you to load dummy data into the preview canvas in Xcode so you can see how your data looks. Next, after the preview property, add the PersistentContainer as a property and declare the init method. The NSPersistentContainer class is a fairly simple class. Given a data model, which you just created, it creates the underlying managedObject model, the managedObjectContext, and the PersistenceStoreCoordinator for you. Inside the init method, create an instance of a PersistentContainer. The initializer for this class takes a name, which sets the name of the persistent store. It's also used to look up the name of the NSManagedObjectModel object used with the NSPersistentContainer object. Since you named the data model RocketLaunches, by providing the same name for the PersistentContainer, you're ensuring that the managedObject model will use the models you defined in the exe datamodeld file. Then add an if statement to check if you're dealing with an in-memory instance of the PersistenceController, and if so, set the container's persistentStoreDescription URL to /dev/null. The only thing left to do now is to complete the creation of the Core Data stack by calling the loadPersistentStores method. The method takes a completion block with two arguments, and an instance of NSPersistentStoreDescription, which is an object that allows you to customize, create and load the underlying store, and an error value if the creation of the stack failed. You won't be doing any customizing, so you can ignore that first argument. In the event that there's an error for the sake of simplicity, you can go ahead and log the error and crash the app. Lastly, set up properties on the viewContext to help later on when you work with Core Data asynchronously. These properties help define some rules when merging data from various threads and also give the viewContext a name, which will help differentiate it from others you'll create later on. You should know that moving forward for your own projects, adding the code you just added is as simple as checking the Use Core Data checkbox when creating a new project. Both the data model file and the persistence.swift file is automatically added for you. Before putting this to use, let's review everything you learned in the next video.