[next] ref accepts arrays
#475
Open
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
titoBouzout
changed the title
use:, remove magic refs, make `ref accept arraysuse:, remove magic refs, make ref accept arrays
This was referenced Nov 10, 2025
titoBouzout
force-pushed
the
ref-arrays-remove-use-remove-magic-ref
branch
from
09e689f to
e2868f1
Compare
titoBouzout
changed the title
use:, remove magic refs, make ref accept arraysref accepts arrays
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In an attempt to deprecate
use:by proposing to usenamed refs(#445) in https://discord.com/channels/722131463138705510/1435384712443990096 ; It became evident that what people need ismerging refs., thats done by supportingarrayvalues in refs.This PR add support for that. Such
<div ref={[props.ref, myRef]}/>Related:
ref:namespace #445