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?
Let's talk about using multi-store pattern in TCA as a way to improve the performance and maintainability.
Subscribe to premium membership plan
Get access to all premium content and enjoy reading without any distraction
Last week I spoke at NSSpainX to talk about how to use Composable Architecture in larger projects, the kind of issues you might run into and how you can work around them. Mentioned articles are: - Exhaustive testing in TCA - TCA Action Boundaries - TCA Action Boundries - Convenience
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.
To maintain our codebases for years, we must create boundaries across modules. Here's my approach to doing that with The Composable Architecture.