Skip to content

[0.78] Properly handle null values in TM interop layer #785

@cipolleschi

Description

@cipolleschi

Target Branch(es)

0.78

Link to commit or PR to be picked

facebook/react-native#49291

Description

The linked PR targets 0.78-stable and it mimics this other PR on main facebook/react-native#49250

The 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type Pick RequestPick requests to include commits inside a React Native release

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions