-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[0.77] Properly handle null values in TM interop layer #786
Labels
Type Pick Request
Pick requests to include commits inside a React Native release
Comments
Thank you for opening a new pick-request for React Native. If your pick does not satisfy the criteria below, please close it as it will not be considered. ✅ Which pick requests we accept
❌ Which pick requests we don’t accept
ℹ️ What makes for a good pickIn order for your pick to be considered, please do the following:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Target Branch(es)
0.77
Link to commit or PR to be picked
facebook/react-native#49298
Description
The linked PR targets
0.77-stable
and it mimics this other PR onmain
facebook/react-native#49250The original PR has not landed in
main
yet, but we need it if we want to prepare a golden release candidate.The problem we are seeing is that some legacy module were passing null values from JS to Native and the null value was used in native to make business logic decisions.
In the New Architecture, null values passed down from JS to Native are stripped out and native does not receive them.
This break some Legacy Libraries that are not migrated to the New Architecture yet.
This change fixes this problem and properly forward null values to modules working throught the interop layer.
The text was updated successfully, but these errors were encountered: