Nick Lockwood 9d0242fdc3 Replace direct access of NativeModules.UIManager with require('UIManager') ... Summary: public Due to the cross-platform polyfills we have added (and will add in future) to `UIManager.js`, accessing UIManager directly via NativeModules instead of importing the wrapper is discouraged. This diff fixes a few places where we were doing this inside our own modules. Note: As a general policy, we should avoid accessing modules via NativeModules anyway. Using wrapper classes allows us to provide static declarations for all the native methods and properties, which can be checked at build time by flow. If we access the modules directly, those interfaces are only known at runtime. Reviewed By: vjeux Differential Revision: D2881300 fb-gh-sync-id: 6737358ea8ea6d722cc1941a4b9fa0123a87fc29		2016-01-30 07:36:34 -08:00
..
FBSnapshotTestCase	Bugfix - Typos	2015-12-15 09:09:32 -08:00
RCTTest.xcodeproj	Introduce SnapshotView which wraps Renderable content and will verify the snapshot	2015-10-02 12:15:24 -07:00
RCTSnapshotManager.h	Introduce SnapshotView which wraps Renderable content and will verify the snapshot	2015-10-02 12:15:24 -07:00
RCTSnapshotManager.m	RCTImagePicker now uses main thread	2015-11-16 03:17:29 -08:00
RCTTestModule.h	Migrate unit tests from FBReactKitModules to FBReactKit	2015-07-07 16:39:35 -08:00
RCTTestModule.m	Standardize Error objects for Promises	2016-01-19 12:20:37 -08:00
RCTTestRunner.h	Move JS integration tests to root folder	2015-11-18 09:35:19 -08:00
RCTTestRunner.m	Wait for JSExecutor to tear down in RCTBridgeTests	2016-01-05 15:30:33 -08:00
SnapshotViewIOS.android.js	Move SnapshotView to SnapshotViewIOS and create an unimplemented android version	2015-10-13 11:48:38 -07:00
SnapshotViewIOS.ios.js	Replace direct access of NativeModules.UIManager with require('UIManager')	2016-01-30 07:36:34 -08:00