From 8c4912a42f0dcab709c1843e6e63308729295d4b Mon Sep 17 00:00:00 2001 From: Joshua Gross Date: Wed, 25 Aug 2021 13:07:31 -0700 Subject: [PATCH] Fabric should be enabled or disabled app-wide without entrypoint-specific options Summary: Add new ReactFeatureFlag to enable or disable Fabric appwide. Changelog: [Internal] Reviewed By: fkgozali Differential Revision: D30504714 fbshipit-source-id: f615d4c888a89f5401b0ff8f8305fdfbdf75fba3 --- .../java/com/facebook/react/config/ReactFeatureFlags.java | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/ReactAndroid/src/main/java/com/facebook/react/config/ReactFeatureFlags.java b/ReactAndroid/src/main/java/com/facebook/react/config/ReactFeatureFlags.java index 8513e6c0ccd..077eb5fd7b2 100644 --- a/ReactAndroid/src/main/java/com/facebook/react/config/ReactFeatureFlags.java +++ b/ReactAndroid/src/main/java/com/facebook/react/config/ReactFeatureFlags.java @@ -25,6 +25,12 @@ public class ReactFeatureFlags { */ public static volatile boolean useTurboModules = false; + /** + * Should this application use the new (Fabric) Renderer? If yes, all rendering in this app will + * use Fabric instead of the legacy renderer. + */ + public static volatile boolean enableFabricRenderer = false; + /** * After TurboModules and Fabric are enabled, we need to ensure that the legacy NativeModule isn't * isn't used. So, turn this flag on to trigger warnings whenever the legacy NativeModule system