[react] Require initial value for useRef
#64920
Closed
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
This was referenced Mar 28, 2023
eps1lon
force-pushed
the
feat/react/useRef-required
branch
from
f8d98e5 to
40d0aa6
Compare
eps1lon
force-pushed
the
feat/react/useRef-required
branch
from
40d0aa6 to
87d2639
Compare
This was referenced Mar 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Implements https://twitter.com/dan_abramov/status/1640157848167489541
Stacked on #64896 (Diff against #64896)
useRefnow requires an explicit initial value. This is in line with documentation andcreateContextJust like for
const current: T | null = useRef<T>(null).currentwe'll have a convenience overload foruseRef<T>(undefined)that ensuresref.currentwill beT | undefined.