fix: Remove potential race conditions from setState changes #2474
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
brianoqr
changed the title
NiharR27
approved these changes
Mar 3, 2024
|
Fixed by #2493 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, so i was using react-native-gifted-chat and had a race condition because my stream of messages happened at the same time as the "onLayout" event which made the isInitialized variable remain false as it was overwritten by a stale state value when the messages array was updated at the same time as onLayout. This happens because setState is being called using a the local state value.
I updated all the setState functions to use the state value passed by the function which is always up to date so you don't have any possibility of writing to state with a stale value.