From e95e15b6d6c8cc326074b647eb2b789de3962e05 Mon Sep 17 00:00:00 2001 From: Hari Krishnan U Date: Fri, 19 Nov 2021 20:52:43 +0530 Subject: [PATCH] Update Part-1.md --- stack/book/Part-1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/stack/book/Part-1.md b/stack/book/Part-1.md index bac89d7..6619b08 100644 --- a/stack/book/Part-1.md +++ b/stack/book/Part-1.md @@ -6,7 +6,7 @@ ### Transaction -Well, the component instance should be somehow **connected** to React's eco-system and, of course, **make some influence** on it. There is a dedicated module `ReactUpdates` which helps with this. As you know, **React performs updates in chunks**, it means that it collects operations and performs them **together**. It’s always better because it allows applying some **pre-condition** and **post-conditions** just once for the whole list of items (chunk) instead of doing it for each item. +Well, the component instance should be somehow **connected** to React's eco-system and, of course, **make some influence** on it. There is a dedicated module `ReactUpdates` which helps with this. As you know, **React performs updates in chunks**, which means that it collects operations and performs them **together**. It’s always better because it allows applying some **pre-condition** and **post-conditions** just once for the whole list of items (chunk) instead of doing it for each item. What actually helps handle this pre/post processing? Right, **transaction**! For someone it can be a new word, or at least its interpretation for UI needs, so let’s talk a bit more about it and start from a simple example.