🆓 The Composable Architecture has reached a major milestone: version 1.0. To celebrate this release we are doing a fresh tour of the library so that folks can become comfortable building applications with it in its most modern form. We will start with a simple, but substantial application that shows off the basics, before we recreate Apple's most complex sample project.

🔒 We continue our tour of the Composable Architecture 1.0 by rebuilding one of Apple's most complex sample projects: Scrumdinger. We will create our own "Standups" app using the tools of the Composable Architecture.

🔒 What's the point of the work we did to make async testing reliable and deterministic, and are

we even testing reality anymore? We conclude our series by rewriting our feature and tests

using Combine instead of async-await, and comparing both approaches.

🔒 We continue our deep dive into advanced Swift concurrency by exploring the concept of "executors" to better understand its global enqueue hook. We will then put this hook to work and finally have reliable, 100% deterministic async tests.

🔒 We dive into Apple's Async Algorithms package to explore some advanced usages of Swift's concurrency runtime, including a particular tool we can leverage to bend the will of async code to our advantage in tests.

🆓 We explore a few more advanced scenarios when it comes to async code—including cancellation, async sequences, and clocks—and how difficult they are to test.

🆓 While Swift provides wonderful tools for writing async code, there are gaps in its tools for testing it. Let's explore the tools it *does* provide to show where they succeed, and where they fall short.

🔒 We complete the series by writing a comprehensive test suite for our stack navigation-based

app. We will uncover some shortcomings of the tools we've built and address each one,

resulting in a set of tools that are a joy to test with.

🔒 We round out the functionality of the Composable Architecture's stack navigation tools. This includes automatic cancellation of a child feature's effects when it's popped off the stack, and the ability for a child feature to pop itself. Along the way we will clean up the domain modeling and user experience of working with these tools.

🔒 We introduce a complementary `StackState` wrapper to our navigation tools to solve a few

issues that came from repurposing the identified array type. Once implemented and integrated,

we will put these tools' superpowers to work by implementing two new features.