Fix comments in ReactFeatureFlags (#42025)

Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/42025

Fix comments in ReactFeatureFlags

changelog: [internal] internal

Reviewed By: arushikesarwani94

Differential Revision: D52263484

fbshipit-source-id: adb598cf7e35d20893cca77e378bde4cab45f857
This commit is contained in:
David Vacca
2024-01-12 09:20:31 -08:00
committed by Facebook GitHub Bot
parent 0b14eed185
commit 1a6f97f947
@@ -21,8 +21,8 @@ import com.facebook.react.common.build.ReactBuildConfig;
public class ReactFeatureFlags {
/**
* Should this application use TurboModules? If yes, then any module that inherits {@link
* com.facebook.react.internal.turbomodule.core.interfaces.TurboModule} will NOT be passed in to
* C++ CatalystInstanceImpl
* com.facebook.react.turbomodule.core.interfaces.TurboModule} will NOT be passed in to C++
* CatalystInstanceImpl
*/
public static volatile boolean useTurboModules = false;
@@ -168,9 +168,9 @@ public class ReactFeatureFlags {
/*
* When the app is completely migrated to Fabric, set this flag to true to
* disable parts of Paper infrastructre that are not needed anymore but consume
* disable parts of Paper infrastructure that are not needed anymore but consume
* memory and CPU. Specifically, UIViewOperationQueue and EventDispatcherImpl will no
* longer work as they won't subscribe to ReactChoregrapher for updates.
* longer work as they won't subscribe to ReactChoreographer for updates.
*/
public static boolean enableFabricRendererExclusively = false;