From 884e242922dfa0a8da5a3c80c45c73be150fa795 Mon Sep 17 00:00:00 2001 From: Website Deployment Script Date: Thu, 8 Feb 2018 17:40:37 +0000 Subject: [PATCH] Deploy website Deploy website version based on 0bd4a448653b0af8dbe1e5e6e03c89784163c1aa --- docs/next/direct-manipulation.html | 2 +- docs/next/running-on-device.html | 7 +++++-- 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/next/direct-manipulation.html b/docs/next/direct-manipulation.html index 8f253a140c7..5dd38da534a 100644 --- a/docs/next/direct-manipulation.html +++ b/docs/next/direct-manipulation.html @@ -171,7 +171,7 @@ render() { >

Avoiding conflicts with the render function

If you update a property that is also managed by the render function, you might end up with some unpredictable and confusing bugs because anytime the component re-renders and that property changes, whatever value was previously set from setNativeProps will be completely ignored and overridden.

setNativeProps & shouldComponentUpdate

-

By intelligently applying shouldComponentUpdate you can avoid the unnecessary overhead involved in reconciling unchanged component subtrees, to the point where it may be performant enough to use setState instead of setNativeProps.

+

By intelligently applying shouldComponentUpdate you can avoid the unnecessary overhead involved in reconciling unchanged component subtrees, to the point where it may be performant enough to use setState instead of setNativeProps.

Other native methods

The methods described here are available on most of the default components provided by React Native. Note, however, that they are not available on composite components that aren't directly backed by a native view. This will generally include most components that you define in your own app.

measure(callback)

diff --git a/docs/next/running-on-device.html b/docs/next/running-on-device.html index 4754236cb5c..118a2831ea8 100644 --- a/docs/next/running-on-device.html +++ b/docs/next/running-on-device.html @@ -206,7 +206,10 @@ emulator-5554 offline

Run the following in a command prompt:

-
$ adb reverse tcp:8081 tcp:8081
+
$ adb -s <device name> reverse tcp:8081 tcp:8081
+

+
To find the device name, run the following adb command:

+
$ adb devices
 

 
You can now enable Live reloading from the Developer menu. Your app will reload whenever your JavaScript code has changed.

 
Method 2: Connect via Wi-Fi

@@ -223,7 +226,7 @@ emulator-5554 offline   red screen with an error. This is OK. The following steps will fix that.
 
  • Open the in-app Developer menu.
    • 
-
  • Go to Dev Settings → Debug server host for device.
    • 
+
  • Go to Dev Settings → Debug server host & port for device.
    • 
 
  • Type in your machine's IP address and the port of the local dev server (e.g. 10.0.1.1:8081).
    • 
 
  • Go back to the Developer menu and select Reload JS.
    •