[Navigator] Support the ref
prop on scene roots
#1361
Closed
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.
Navigator overrides the
ref
prop of scene components so that it can callonItemRef
and do internal bookkeeping. With callback refs, we can additionally call the original value of theref
prop as long as it's a function (that is, string refs are not supported). Note that theref
prop is moved toreactElement.ref
out ofreactElement.props.ref
, which is why this diff accesseschild.ref
.This diff adds support for callback refs and warns helpfully if a string ref was provided. It should be completely backwards compatible since scenes couldn't have been relying on the
ref
prop before.cc @ericvicenti
Test Plan: Write a renderScene implementation that puts a callback ref on the root component: