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.
Converting prototype component system to data-driven w/ live reloading & automation using Sourcery for easier maintenance & reliability
Let's start exploring a component-based architecture slightly different from the usual patterns we use.
What are your favorite Swift debugging tips?
Subscribe to premium membership plan
Get access to all premium content and enjoy reading without any distraction
How to evaluate problem areas you see in day-to-day development to assess whether they could be solved at a scale of your team/company or the whole community?
Now that we added some structure to our TCA actions, let's add automation and convenience API's.
How often have you wanted to change some small setting in your application? Let's build a generic solution.
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.