Fabric: Removed leftovers from RCTScheduler

Summary: Trivial. We use `EventBeatFactory`s instead. Reviewed By: mdvacca Differential Revision: D9799856 fbshipit-source-id: 67a130161026565ecc948427ffa658837d9bbfc2
facebook · Sep 14, 2018 · a3752c6 · a3752c6
1 parent e05acf1
commit a3752c6
Showing 1 changed file with 0 additions and 3 deletions.
diff --git a/React/Fabric/RCTScheduler.mm b/React/Fabric/RCTScheduler.mm
@@ -69,9 +69,6 @@ - (instancetype)init
     contextContainer->registerInstance<EventBeatFactory>(synchronousBeatFactory, "synchronous");
     contextContainer->registerInstance<EventBeatFactory>(asynchronousBeatFactory, "asynchronous");
 
-    contextContainer->registerInstance<std::shared_ptr<EventBeat>>(std::make_shared<MainRunLoopEventBeat>(), "synchronous");
-    contextContainer->registerInstance<std::shared_ptr<EventBeat>>(std::make_shared<MessageQueueEventBeat>(bridge.jsMessageThread), "asynchronous");
-
     void *imageLoader = (__bridge void *)[[RCTBridge currentBridge] imageLoader];
     contextContainer->registerInstance(std::make_shared<ImageManager>(imageLoader));