Integrate Combine Into an App

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

There's one more thing you'll do to the model before moving on, make it conform to ObservableObject, so that it can be observed throughout the app. What exactly does this do? For types that adopt ObserverbleObject, the compiler will automatically synthesize and object will change property, which is a publisher. And this gets called before the object changes. So any subscriber can be made aware. Adoption of this protocol also allows the object to used inside views. This along with the @Published properties we discussed in an earlier episode, helped tell the view when to refresh. Speaking of which, we know publishers don't exist in isolation, they need to have subscribers to start the flow of data. Luckily, there's a corresponding property wrapper in SwiftUI when working with models that adopt ObservableObject, and that's @ObservedObject. When this pairing occurs in your code, a binding is established between your view and the external model, unlike with @State where bindings happen within views. At that point, the steps are very familiar. When the external model changes, and the @Published properties publish their new values, the views that have that model decorated with an observed object, will receive that change and update their body properties. Let's take a quick look at the code needed for this change. In the JokesViewModel.swift file make JokesViewModel adopt ObservableObject. Now over in views, JokeCardView.swift decorate the viewModel with the @ObservedObject property wrapper. Views JokeView.swift also has a viewModel. So add the @ObservedObject property wrapper here as well. Great, our publishers are built and now hooked into our viewModel. Now we move on to our next feature. Storing like jokes in a Core Data database, which we'll do next.