In my previous article, I talked about the need to create boundaries and structure around TCA Actions.
Let's build on top of that:
- Introduce improved APIs
- Add compile-time errors if someone tries to break the boundaries
- Showcase a more experimental Reducer creation
This post is for paying subscribers only
Sign up now to read this article and get access to all premium posts.
Already have an account? Sign In
Subscribe to premium membership plan
Get access to all premium content and enjoy reading without any distraction