From 06adff2e2fc8a6975eb306e3bc32dda773444bd3 Mon Sep 17 00:00:00 2001 From: Website Deployment Script Date: Sat, 25 Aug 2018 15:04:29 +0000 Subject: [PATCH] Deploy website Deploy website version based on 0a19ef38b11bc8d2585cc855c4770098b73bb8fa --- docs/next/direct-manipulation.html | 2 +- docs/next/direct-manipulation/index.html | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/next/direct-manipulation.html b/docs/next/direct-manipulation.html index 99704eee9e8..46b26cd2ce1 100644 --- a/docs/next/direct-manipulation.html +++ b/docs/next/direct-manipulation.html @@ -68,7 +68,7 @@ render() { }

This is computationally intensive compared to the original example - React needs to re-render the component hierarchy each time the opacity changes, even though other properties of the view and its children haven't changed. Usually this overhead isn't a concern but when performing continuous animations and responding to gestures, judiciously optimizing your components can improve your animations' fidelity.

-

If you look at the implementation of setNativeProps in NativeMethodsMixin.js you will notice that it is a wrapper around RCTUIManager.updateView - this is the exact same function call that results from re-rendering - see receiveComponent in ReactNativeBaseComponent.js.

+

If you look at the implementation of setNativeProps in NativeMethodsMixin you will notice that it is a wrapper around RCTUIManager.updateView - this is the exact same function call that results from re-rendering - see receiveComponent in ReactNativeBaseComponent.js.

Composite components and setNativeProps

Composite components are not backed by a native view, so you cannot call setNativeProps on them. Consider this example: