From d3dd0da656de9f45578d5e1b2931b14c388ac208 Mon Sep 17 00:00:00 2001 From: Yu Tawata Date: Wed, 27 Nov 2019 20:07:56 +0900 Subject: [PATCH] Fixed link (#39) * Fix link for ep.78 * Fix link for ep.82 --- 0078-effectful-state-management-async-effects/README.md | 2 +- 0082-testable-state-management-reducers/README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/0078-effectful-state-management-async-effects/README.md b/0078-effectful-state-management-async-effects/README.md index d02b75fb..467cc82d 100644 --- a/0078-effectful-state-management-async-effects/README.md +++ b/0078-effectful-state-management-async-effects/README.md @@ -1,5 +1,5 @@ ## [Point-Free](https://www.pointfree.co) -> #### This directory contains code from Point-Free Episode: [Effectful State Management: Unidirectional Effects](https://www.pointfree.co/episodes/ep77-effectful-state-management-unidirectional-effects) +> #### This directory contains code from Point-Free Episode: [Effectful State Management: Asynchronous Effects](https://www.pointfree.co/episodes/ep78-effectful-state-management-asynchronous-effects) > > It's time to finish our architecture's story for side effects. We've described synchronous effects and unidirectional effects, but we still haven't captured the complexity of async effects. Let's fix that with a final, functional refactor. diff --git a/0082-testable-state-management-reducers/README.md b/0082-testable-state-management-reducers/README.md index a79ef7fe..b48ab000 100644 --- a/0082-testable-state-management-reducers/README.md +++ b/0082-testable-state-management-reducers/README.md @@ -1,5 +1,5 @@ ## [Point-Free](https://www.pointfree.co) -> #### This directory contains code from Point-Free Episode: [Testable State Management: Reducers](https://www.pointfree.co/episodes/0082-testable-state-management-reducers) +> #### This directory contains code from Point-Free Episode: [Testable State Management: Reducers](https://www.pointfree.co/episodes/ep82-testable-state-management-reducers) > > It's time to see how our architecture handles the fifth and final problem we identified as being important to solve when building a moderately complex application: testing! Let's get our feet wet and write some tests for all of the reducers powering our application.