Add useLatestRef() and useLayoutLatestRef() #2509
Open
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
pastelmind
force-pushed
the
pr/use-latest-ref
branch
from
c8a5f57
to
580dfab
Compare
pastelmind
force-pushed
the
pr/use-latest-ref
branch
from
580dfab
to
0da9c84
Compare
|
Nice PR! |
|
Really hope this is merged. useLatest is not safe. |
|
Is there any progress? |
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.
Description
This PR adds two hooks
useLatestRef()anduseLayoutLatestRef()as described in #2328 (comment). They are similar touseLatest(), but avoid updating the ref directly during render, which is deemed unsafe by the React team..This PR also marks
useLatest()as@deprecatedand recommenduseLatestRef()as an alternative.Type of change
Checklist
yarn test)yarn lint). Fix it withyarn lint:fixin case of failure.yarn lint:types).