Move message queue initialization in ReactContext into its own method

Summary: Refactoring ReactContext to move message queue initialization into its own function that can be called independently of initializeWithInstance. This allows you to create a ReactContext with message queue threads without a CatalystInstance.

Reviewed By: mdvacca

Differential Revision: D15246287

fbshipit-source-id: 4b8c53e68112af7eded47d8c31311500cc296dfe
This commit is contained in:
Emily Janzer
2019-05-09 15:49:18 -07:00
committed by Facebook Github Bot
parent 1d985b5e6e
commit db40c28728
@@ -65,6 +65,17 @@ public class ReactContext extends ContextWrapper {
mCatalystInstance = catalystInstance;
ReactQueueConfiguration queueConfig = catalystInstance.getReactQueueConfiguration();
initializeMessageQueueThreads(queueConfig);
}
/**
* Initialize message queue threads using a ReactQueueConfiguration.
* TODO (janzer) T43898341 Make this package instead of public
*/
public void initializeMessageQueueThreads(ReactQueueConfiguration queueConfig) {
if (mUiMessageQueueThread != null || mNativeModulesMessageQueueThread != null || mJSMessageQueueThread != null) {
throw new IllegalStateException("Message queue threads already initialized");
}
mUiMessageQueueThread = queueConfig.getUIQueueThread();
mNativeModulesMessageQueueThread = queueConfig.getNativeModulesQueueThread();
mJSMessageQueueThread = queueConfig.getJSQueueThread();