mirror of
https://github.com/facebook/react-native.git
synced 2025-11-01 09:14:26 +00:00
Ramanpreet Nara
41d948c8d6
Summary: We need to instrument the following markers for TurboModules in Java: - **Java:** moduleDataCreate - **Java:** moduleCreate **Problem:** Perf-logging can be on or off in production. This means that we have to guard every perf-logger call, which can be a bit tedious. Therefore, this diff introduces a Java class called `TurboModulePerfLogger`, which: 1. Enables perf-logging by accepting a `NativeModulePerfLogger` `jni::HybridObject` in its `enableLogging` method. 2. Exposes static methods that call into the `NativeModulePerfLogger`'s Java part, when perf-logging is enabled. We actually have C++ markers as well: - **C++:** moduleJSRequireBeginning - **C++:** moduleJSRequireEnding - **C++:** syncMethodCall - **C++:** asyncMethodCall - **C++:** asyncMethodCallExecution Therefore, `TurboModulePerfLogger.java` also calls its native method `jniEnableCppLogging` to setup C++ TurboModule perf-logging. TurboModule C++ logging is done via a similar setup (to Java), using `TurboModulePerfLogger.cpp`. The `jniEnableCppLogging` native method calls into `TurboModulePerfLogger::enableLogging` with the C++ part of `NativeModulePerfLogger`. Then, the TurboModules C++ infra uses the static methods on `TurboModulePerfLogger.cpp` to start/end markers. Changelog: [Internal] Reviewed By: PeteTheHeat Differential Revision: D22444246 fbshipit-source-id: 66f191056cdcf5d7932ff1916a1de70b82e5f32b
Building React Native for Android
See the docs on the website.
Running tests
When you submit a pull request CircleCI will automatically run all tests. To run tests locally, see Testing.