From 9350eb671f463cb0e32b4547fd1ab022212d91c3 Mon Sep 17 00:00:00 2001 From: balavishnu-vj Date: Tue, 12 Jun 2018 01:30:08 +0530 Subject: [PATCH] Update 2018-06-07-you-probably-dont-need-derived-state.md (#958) Typo: I think it should be props.list instead of props.items. --- content/blog/2018-06-07-you-probably-dont-need-derived-state.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/2018-06-07-you-probably-dont-need-derived-state.md b/content/blog/2018-06-07-you-probably-dont-need-derived-state.md index 7b51cb3c..2815ec46 100644 --- a/content/blog/2018-06-07-you-probably-dont-need-derived-state.md +++ b/content/blog/2018-06-07-you-probably-dont-need-derived-state.md @@ -338,7 +338,7 @@ When using memoization, remember a couple of constraints: 1. In most cases, you'll want to **attach the memoized function to a component instance**. This prevents multiple instances of a component from resetting each other's memoized keys. 1. Typically you'll want to use a memoization helper with a **limited cache size** in order to prevent memory leaks over time. (In the example above, we used `memoize-one` because it only caches the most recent argument and result.) -1. None of the implementations shown in this section will work if `props.items` is recreated each time the parent component renders. But in most cases, this setup is appropriate. +1. None of the implementations shown in this section will work if `props.list` is recreated each time the parent component renders. But in most cases, this setup is appropriate. ## In closing