mirror of
https://github.com/facebook/react-native.git
synced 2025-11-01 09:14:26 +00:00
Clean up RAIICallbackManager experiment
Summary: This experiment was shipped in D27436402 (https://github.com/facebook/react-native/commit/3d1afbbda301d48a75e45f73b96cd51ae5105dd8). Changelog: [Internal] Reviewed By: JoshuaGross Differential Revision: D30023039 fbshipit-source-id: 5f7335f2ddaf6f4e2d876a917aaff2cf3d906b5c
This commit is contained in:
committed by
Facebook GitHub Bot
parent
3ed3d34987
commit
1e4dd5e877
@@ -25,13 +25,6 @@ public class ReactFeatureFlags {
|
||||
*/
|
||||
public static volatile boolean useTurboModules = false;
|
||||
|
||||
/**
|
||||
* Should application use the new TM callback manager in Cxx? This is assumed to be a sane
|
||||
* default, but it's new. We will delete once (1) we know it's safe to ship and (2) we have
|
||||
* quantified impact.
|
||||
*/
|
||||
public static volatile boolean useTurboModulesRAIICallbackManager = false;
|
||||
|
||||
/** Should we dispatch TurboModule methods with promise returns to the NativeModules thread? */
|
||||
public static volatile boolean enableTurboModulePromiseAsyncDispatch = false;
|
||||
|
||||
|
||||
Reference in New Issue
Block a user