From 1fa56a0ac4ae24a01811db4cf23c3264c60ac342 Mon Sep 17 00:00:00 2001 From: Karan Thakkar Date: Sat, 17 Nov 2018 21:39:04 -0800 Subject: [PATCH] Rename requiresMainThreadSetup -> requiresMainQueueSetup in code comment (#22328) Summary: Update reference to property in code comment in `RCTBridgeModule`. There is no such thing as `requiresMainThreadSetup` in the codebase. Its called `requiresMainQueueSetup` now. Pull Request resolved: https://github.com/facebook/react-native/pull/22328 Differential Revision: D13115352 Pulled By: shergin fbshipit-source-id: 511d627388b51029821c4b1ddf4caac30e573040 --- React/Base/RCTBridgeModule.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/React/Base/RCTBridgeModule.h b/React/Base/RCTBridgeModule.h index 729a6d6f5..a01e4117a 100644 --- a/React/Base/RCTBridgeModule.h +++ b/React/Base/RCTBridgeModule.h @@ -301,7 +301,7 @@ RCT_EXTERN void RCTRegisterModule(Class); \ * for the lifetime of the bridge, so it is not suitable for returning dynamic values, but may be used for long-lived * values such as session keys, that are regenerated only as part of a reload of the entire React application. * - * If you implement this method and do not implement `requiresMainThreadSetup`, you will trigger deprecated logic + * If you implement this method and do not implement `requiresMainQueueSetup`, you will trigger deprecated logic * that eagerly initializes your module on bridge startup. In the future, this behaviour will be changed to default * to initializing lazily, and even modules with constants will be initialized lazily. */