Knowing Combine’s feature set, you can identify areas of your code where using a Combine pipeline would be most beneficial, which will allow you to keep your app up to date and provide the best user experience possible. In this episode, use the requirements of the Jokes…

Publishers are only part of the Combine pipeline; they have to be subscribed to in order to start the data flowing. In this episode, learn how the Publishers you’ve made can be used in the ViewModel that will drive the user interface…

Property Wrappers in Combine allow state to easily become published to your app’s SwiftUI views. In this episode, you’ll learn how to use the @Published property wrapper and the ObservableObject protocol to get your models ready to be used by SwiftUI…

…with all other code, your Combine pipeline code can, and should be, tested. The Given-When-Then pattern is a great way to layout your test code, ensuring that your code works as intended…

Earlier when we defined places we could use Combine in our Jokes app, we determined that fetching a list of saved jokes would be a great piece of functionality to show off the powers of Combine - but we need to have data in the database before we can do that…

Your app has to get data from a source in order to use it. The Publisher-Subscriber paradigm seen in Combine seems like a natural fit here, so in this episode, learn how to create custom publishers to help deliver jokes and translations to your model…

…will allow us - as we saw in the last episode - to save and delete content from the database. Note that this isn’t using Combine per se, but instead allows us to use Combine in the next episode. As a quick reminder, a context in this case is like…