react-native/ReactCommon/fabric/components/switch/SwitchShadowNode.cpp

/**
 * Copyright (c) 2015-present, Facebook, Inc.
 *
 * This source code is licensed under the MIT license found in the
 * LICENSE file in the root directory of this source tree.
 */

#include "SwitchShadowNode.h"

namespace facebook {
namespace react {

extern const char SwitchComponentName[] = "Switch";

} // namespace react
} // namespace facebook
Fabric: Implemetation of <Switch> component Summary: This is pretty straightforward implementation uses native `UISwitch`. Suddenly we need Switch to test a bunch of other things. Reviewed By: fkgozali Differential Revision: D8344055 fbshipit-source-id: cfc51b8bc11198eb9d4d5e4745b96fb3a7f14de1 2018-06-15 11:25:16 -07:00			`/**`
			`* Copyright (c) 2015-present, Facebook, Inc.`
			`*`
			`* This source code is licensed under the MIT license found in the`
			`* LICENSE file in the root directory of this source tree.`
			`*/`

Fabric: Simplified way to specialize ComponentName in ConcreteShadowNode class template Summary: @public Previously, all ConcreteShadowNode subclasses had to override `getComponentName()` function to specialize a name of the component. And often it was all that those subclasses do. Now, it's a template argument; and many ShadowNode classes can be created as oneliners via just specializing ConcreteShadowNode template. Unfortunately, C++ does not allow to use `std::string`s or string literals as template arguments, but it allows to use pointers. Moreover, those pointers must point to some linked data, hence, those values must be declared in .cpp (not .h) files. For simplicity, we put those constants in Props classes, (but this is not a strong requirement). Reviewed By: mdvacca Differential Revision: D8942826 fbshipit-source-id: 4fd517e2485eb8f8c20a51df9b3496941856d8a5 2018-08-04 09:30:13 -07:00			`#include "SwitchShadowNode.h"`
Fabric: Implemetation of <Switch> component Summary: This is pretty straightforward implementation uses native `UISwitch`. Suddenly we need Switch to test a bunch of other things. Reviewed By: fkgozali Differential Revision: D8344055 fbshipit-source-id: cfc51b8bc11198eb9d4d5e4745b96fb3a7f14de1 2018-06-15 11:25:16 -07:00
			`namespace facebook {`
			`namespace react {`

Fabric: Simplified way to specialize ComponentName in ConcreteShadowNode class template Summary: @public Previously, all ConcreteShadowNode subclasses had to override `getComponentName()` function to specialize a name of the component. And often it was all that those subclasses do. Now, it's a template argument; and many ShadowNode classes can be created as oneliners via just specializing ConcreteShadowNode template. Unfortunately, C++ does not allow to use `std::string`s or string literals as template arguments, but it allows to use pointers. Moreover, those pointers must point to some linked data, hence, those values must be declared in .cpp (not .h) files. For simplicity, we put those constants in Props classes, (but this is not a strong requirement). Reviewed By: mdvacca Differential Revision: D8942826 fbshipit-source-id: 4fd517e2485eb8f8c20a51df9b3496941856d8a5 2018-08-04 09:30:13 -07:00			`extern const char SwitchComponentName[] = "Switch";`
Fabric: Implemetation of <Switch> component Summary: This is pretty straightforward implementation uses native `UISwitch`. Suddenly we need Switch to test a bunch of other things. Reviewed By: fkgozali Differential Revision: D8344055 fbshipit-source-id: cfc51b8bc11198eb9d4d5e4745b96fb3a7f14de1 2018-06-15 11:25:16 -07:00
			`} // namespace react`
			`} // namespace facebook`