Continuing series on crafting your very own developer tool, we're delving into the heart of the process! Explore the intricacies of modeling log entries and building a dynamic filtering system that tailors to your needs.
Crafting a dev tool? Here's how I'm implementing an easy-to-use toggle to unveil a more complex UI for my latest project.
Let's explore couple of atypical Sourcery use-cases.
How often have you wanted to change some small setting in your application? Let's build a generic solution.
Subscribe to premium membership plan
Get access to all premium content and enjoy reading without any distraction
Exhaustivity in the context of TCA tests means every test you perform has to replicate all the actions, state changes, and effects steaming from the first trigger you want to verify. It leads to a code that has a lot of TDD anti-patterns. Let’s get into the details.
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
A lot has been written about improving Swift compile times, but the compiler and linker are just part of the equation that slows down our development cycle. Most projects leverage great 3rd party tools like SwiftLint, Sourcery, SwiftGen, SwiftFormat and many more. Leveraging those tools is the right thing to
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