react-native/ReactCommon/fabric/components
Valentin Shergin 52ed882332 Fabric: Using `const ShadowNode &` as a parameter in ShadowNode copy constructor
Summary:
@public
When we copy-construct ShadowNode, we don't need to retain a source shadow node, so there is no need to pass it as a `shared_ptr`. Passing an argument to constructor as `const &` is also more idiomatic in C++.

Reviewed By: mdvacca

Differential Revision: D8988384

fbshipit-source-id: 1279d9185fa1b4b82fd26e3040bd62fa9495b4d3
2018-08-04 09:47:30 -07:00
..
activityindicator Fabric: Simplified way to specialize ComponentName in ConcreteShadowNode class template 2018-08-04 09:47:30 -07:00
image Fabric: Simplified way to specialize ComponentName in ConcreteShadowNode class template 2018-08-04 09:47:30 -07:00
root Fabric: Simplified way to specialize ComponentName in ConcreteShadowNode class template 2018-08-04 09:47:30 -07:00
scrollview Fabric: Simplified way to specialize ComponentName in ConcreteShadowNode class template 2018-08-04 09:47:30 -07:00
switch Fabric: Simplified way to specialize ComponentName in ConcreteShadowNode class template 2018-08-04 09:47:30 -07:00
text Fabric: `ShadowNode::getChildren()` now returns `vector`, not `shared_ptr` 2018-08-04 09:47:30 -07:00
view Fabric: Using `const ShadowNode &` as a parameter in ShadowNode copy constructor 2018-08-04 09:47:30 -07:00