Remove warning when calling measure
from RN runtime
#4526
Merged
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.
Summary
This PR removes a warning that would trigger when
measure
function was called from the main RN runtime.The main motivation behind adding this
console.warn
was to force the developer to explicitly cover the case whenmeasure
is called from the RN runtime usingif (!_WORKLET) { ... }
guard, which, let's be honest, is quite uncomfortable. On the other hand, when measurement cannot be made, e.g. when called from the UI runtime but when the view is not mounted yet,measure
returnsnull
, which needs to be handled withif (measured === null) { ... }
. It makes sense to merge these two cases since they can be handled identically.Test plan