Skip to content

Commit 17ec78d

Browse files
Fix re-sync example in lifecycle-of-reactive-effects
1 parent d917a2b commit 17ec78d

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

src/content/learn/lifecycle-of-reactive-effects.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -284,7 +284,7 @@ The first two logs are development-only. In development, React always remounts e
284284
285285
The main reason your Effect will re-synchronize in practice is if some data it uses has changed. In the sandbox above, change the selected chat room. Notice how, when the `roomId` changes, your Effect re-synchronizes.
286286
287-
However, there are also more unusual cases in which re-synchronization is necessary. For example, try editing the `serverUrl` in the sandbox above while the chat is open. Notice how the Effect re-synchronizes in response to your edits to the code. In the future, React may add more features that rely on re-synchronization.
287+
However, there are also more unusual cases in which re-synchronization is necessary. For example, in development, React may re-synchronize an Effect after you edit its code so that it stays consistent with the latest changes. In the future, React may add more features that rely on re-synchronization.
288288
289289
### How React knows that it needs to re-synchronize the Effect {/*how-react-knows-that-it-needs-to-re-synchronize-the-effect*/}
290290

0 commit comments

Comments
 (0)