b070f05926
Summary: @public With this guard removed, the functionality is the same in RCT_DEV and non-RCT_DEV builds because RCTDevSettings will return NO (or not exist) in non-RCT_DEV builds, so this code will not be run. Pros to this approach: - Hot loading can be enabled in a non-RCT_DEV build Cons: - all builds now have this extra block of code, even if it won't be run If the cons are too strong, I can move this code into a new RCT_DEFINE that inherits from RCT_DEV. (but notably, can be overridden) Reviewed By: shergin Differential Revision: D17118516 fbshipit-source-id: cc6c01cca6b2450c35274eccc939c9a2123e6b93 |
||
---|---|---|
.. | ||
JSCExecutorFactory.h | ||
JSCExecutorFactory.mm | ||
NSDataBigString.h | ||
NSDataBigString.mm | ||
RCTCxxBridge.mm | ||
RCTCxxBridgeDelegate.h | ||
RCTMessageThread.h | ||
RCTMessageThread.mm | ||
RCTObjcExecutor.h | ||
RCTObjcExecutor.mm |