From 07017de81a45b5e8b77190c5dd6bb7d0c7e2c724 Mon Sep 17 00:00:00 2001 From: Brian Vaughn Date: Wed, 6 Jun 2018 14:11:35 -0400 Subject: [PATCH] Added emphasis suggested by Ryan --- 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 2ad6151e..3f65dc84 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 @@ -30,7 +30,7 @@ If you're not sure about whether your component should use derived state, here a * Is the state **derived** from props (as opposed to just mirroring it)? * Is the state update specifically triggered by a **props change** (and not just the current props value)? -If your answer to either of the above questions is "no" then there are better patterns to use! (We'll cover them below.) +If your answer to either of the above questions is “no” (which is almost always the case) then there are better patterns to use! We’ll cover them below. ## When should I avoid derived state?