react-native/ReactCommon/fabric/components/activityindicator/ActivityIndicatorViewShadowNode.cpp

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

#include "ActivityIndicatorViewShadowNode.h"

namespace facebook {
namespace react {

const char ActivityIndicatorViewComponentName[] = "ActivityIndicatorView";

} // namespace react
} // namespace facebook
iOS: Support <ActivityIndicator> component Summary: Setup for using <ActivityIndicator> component in Fabric. Reviewed By: shergin Differential Revision: D8107528 fbshipit-source-id: e3ba46d1538f5d5a2fa6f75639caaaa51156c452 2018-05-23 10:03:41 -07:00			`/**`
Update copyright headers to yearless format Summary: This change drops the year from the copyright headers and the LICENSE file. Reviewed By: yungsters Differential Revision: D9727774 fbshipit-source-id: df4fc1e4390733fe774b1a160dd41b4a3d83302a 2018-09-11 15:27:47 -07:00			`* Copyright (c) Facebook, Inc. and its affiliates.`
iOS: Support <ActivityIndicator> component Summary: Setup for using <ActivityIndicator> component in Fabric. Reviewed By: shergin Differential Revision: D8107528 fbshipit-source-id: e3ba46d1538f5d5a2fa6f75639caaaa51156c452 2018-05-23 10:03:41 -07:00			`*`
			`* 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 "ActivityIndicatorViewShadowNode.h"`
iOS: Support <ActivityIndicator> component Summary: Setup for using <ActivityIndicator> component in Fabric. Reviewed By: shergin Differential Revision: D8107528 fbshipit-source-id: e3ba46d1538f5d5a2fa6f75639caaaa51156c452 2018-05-23 10:03:41 -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			`const char ActivityIndicatorViewComponentName[] = "ActivityIndicatorView";`
iOS: Support <ActivityIndicator> component Summary: Setup for using <ActivityIndicator> component in Fabric. Reviewed By: shergin Differential Revision: D8107528 fbshipit-source-id: e3ba46d1538f5d5a2fa6f75639caaaa51156c452 2018-05-23 10:03:41 -07:00
			`} // namespace react`
			`} // namespace facebook`