Get a stripped down version of the UIExplorer app working. This minimal version excludes the status bar, drawer/navigator tab bar, and removes most of the demos except for simple ones.
Fixes#210
There is an issue with scroll view where the container view was being collapsed by the optimizer. Ensure the 'collapsable' property is picked up.
Fixes#143
The callbacks for AsyncStorageModule expect two parameters, where the first is the list of errors and the second is the results. Ensure that a null error value is inserted into the callback arguments before the results, or that null is sent when no error occurred.
Fixes#260
ClipboardModule provides access to native clipboard for React Native JavaScript applications.
- change ClipboardModule base class to NativeModuleBase from ReactContextNativeModuleBase
Fixes#255
The BackAndroid module provides a JS API for the native DeviceEventEmitter module to hook into back-button presses. This is needed, e.g., for Navigator.
Fixes#246
A key to allowing ReactNative for UWP to differentiate itself is to allow JavaScript customization for native modules and view managers.
This lays the ground work for that by:
* adding the Windows-specific JavaScript exports that are referenced in the core ReactNative modules
* making the necessary changes to ReactPage and the dev support tools.
Fixes#240
When launching the debugger in Chrome, if the debugger window is not yet open, we can attempt to prepare the debug environment before it's ready.
This changeset adds a cancellation after a 5 seconds, and utilizes the 3 possible retries.
This was a pretty trivial setup, given all the infrastructure and designs that were already in place to implement the DevSupportManager.
All we really needed was to investigate the correct format for data on the wire, and implement it.
Currently, we are mimicking the iOS behavior for the NetInfoModule. Eventually, we can add other Windows specific features in the same way Android has.
Rapid storyboard changes can result in incorrect behavior. This set of changes ensures that storyboards execute sequentially and have explicit cancellation semantics.
As it turns out, when you pass a delegate to Chakra to define native functions, make sure you hang on to a reference to that delegate.
The delegates for console.log, console.warn, and console.error were being garbage collected, so when React Native made calls to them, they tried to invoke a delegate that was already garbage collected.
The ChakraJavaScriptExecutor now holds references to these for the entire lifetime of the object.
Eric Rozell
Eero Bragge
Erik Schlegel