838cc48059
Summary:In Jest, we sometimes wipe away the (partial) state of the world. I noticed that when we run the NativeModules file twice, it throws. Because Jest implicitly throws out the state, it isn't obvious what exactly is going on. I figured I'll fix this in react-native directly as I don't see a reason why those fields shouldn't be configurable. This shouldn't have any negative impact on react-native apps themselves. cc ide bestander tadeuzagallo davidaurelio Closes https://github.com/facebook/react-native/pull/6914 Differential Revision: D3162561 Pulled By: cpojer fb-gh-sync-id: d3418ec210278a44f8ad325f7e9e01872b4877d1 fbshipit-source-id: d3418ec210278a44f8ad325f7e9e01872b4877d1 |
||
---|---|---|
.. | ||
__mocks__ | ||
NativeModules.js | ||
NativeModules.js.flow | ||
RCTAlertManager.ios.js | ||
RCTEventEmitter.js |