From 8bcb4839762053a095ee8cbbf3b4f5b471d01181 Mon Sep 17 00:00:00 2001 From: tebb Date: Mon, 27 Mar 2023 11:37:08 +0100 Subject: [PATCH] docs: improve a/hc/lc pattern order explanation (#40) Thank you. This cheatsheet is very useful. If I understood the logic, my changes to README.md may be helpful. If not, sorry :) Also ... Could you add shouldUpdateComponent and shouldComponentUpdate into the table (or an extension to the table below Note:). It isn't obvious to me which columns 'should', 'Update' and 'Component' are in because 'Update' is the verb (action?). Thanks. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 5b1ee6c..04b625d 100644 --- a/README.md +++ b/README.md @@ -140,7 +140,7 @@ Take a look at how this pattern may be applied in the table below. | `handleClickOutside` | | `handle` | `Click` | `Outside` | | `shouldDisplayMessage` | `should` | `Display` | `Message` | | -> **Note:** The order of context affects the meaning of a variable. For example, `shouldUpdateComponent` means _you_ are about to update a component, while `shouldComponentUpdate` tells you that _component_ will update on itself, and you are but controlling when it should be updated. +> **Note:** The order of context affects the meaning of a variable. For example, `shouldUpdateComponent` means _you_ are about to update a component, while `shouldComponentUpdate` tells you that _component_ will update itself, and you are only controlling _when_ it should update. > In other words, **high context emphasizes the meaning of a variable**. ---