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
Subscribe to newsletter
Stay up to date! Get all the latest posts delivered straight to your inbox.
You've successfully subscribed to Krzysztof Zabłocki
Great! Next, complete checkout to get full access to all premium content.
Error! Could not sign up. invalid link.
Welcome back! You've successfully signed in.
Error! Could not sign in. Please try again.
Success! Your account is fully activated, you now have access to all content.
Error! Stripe checkout failed.
Success! Your billing info is updated.
Error! Billing info update failed.