fix: adjust useMounted to work with strict effects #70
Conversation
This file contains hidden or 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
jquense
approved these changes
Mar 29, 2022
|
seems like codecovs broken |
|
Nice fix! I think codecov's been broken for a while now. |
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.
Fix for downsteam: react-bootstrap/react-bootstrap#6284 .
React 18 introduces a new StrictMode mount -> unmount -> mount pattern, which breaks
useMountedin development and by extensionuseSafeStatehook. I don't think there's a way to test this unfortunately(although if you've got any ideas let me know), but I've tested it locally and it fixes the issue that i've linked above.