Let's explore couple of atypical Sourcery use-cases.
How can you leverage masking to build a captivating content reveal effect?
How often have you wanted to change some small setting in your application? Let's build a generic solution.
I've been a fan of Point Free Composable architecture for a while now. I've worked on TCA projects for more than a year on projects of all sizes: from smaller projects like my indie Sourcery Pro, through the New York Times project, to a truly large codebase, a completely new
Subscribe to premium membership plan
Get access to all premium content and enjoy reading without any distraction
Yesterday I was interviewed by Apple Treats You can watch the recording here: Or listen in Apple Podcasts
Two weeks ago I've released Sourcery Pro, the most powerful Xcode extension that exists. If you still didn't check it out, you really should as it can save you 100+ hours by letting you automate a lot of repetitive code in your projects, from writing mocks through SwiftUI and Snapshots.
Codable is a great protocol for automating simple model persistence, but it lacks support for any kind of versioning or migrating the data from older versions. You can, of course, implement custom Codable adherence and throw in a bunch of if statements and manual decoding to achieve this goal, but
If your app has a lot of content, chances are that by the time you get a chance to work on a bug report, the data that the bug appeared on will be long gone. Here are some tidbits on how I created a simple solution for that problem at