Fix useImmediateState for React Native #358
Merged
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
Also leaves a note to react-redux, since they'll likely be looking out for an alternative solution as well
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.
The
ssrcheck was failing on React Native since it was kind of aggressive. I don't really want to even have it oruseLayoutEffectin place, but multiple React threads didn't really resolve concerns that have been raised with it. Evenreact-reduxuses it in this way.I tried to find an alternative solution, but it turns out that
useState(s => s)which would be firing at a similar time still triggers an update.I've left a link to react-redux's repo since they're likely also be looking out for a solution to this problem.