[internal] Refactor useForkRef TS types: tighten cleanupRef and simplify ref typing
#46967
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.
This PR improves the
useForkRefhook by refining the type ofcleanupRefto always be a function, removing unnecessary type assertions on refs, and narrowing theinstanceparameter type inrefEffectfromInstance | nulltoInstance. These changes increase type safety and code clarity:Changed
cleanupReftype fromvoid | (() => void)to() => voidbecause it always holds a cleanup function.Removed redundant
as React.RefObjecttype assertions for cleaner, clearer code.Narrowed
refEffect'sinstanceparameter type since null values are guarded before invocation.I have followed (at least) the PR section of the contributing guide.