react-native/ReactCommon/fabric/core/primitives
Valentin Shergin 67a79010ca 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:47:30 -07:00
..
ReactPrimitives.h Fabric: Simplified way to specialize ComponentName in ConcreteShadowNode class template 2018-08-04 09:47:30 -07:00
Sealable.cpp Fabric: Making Sealable debug-only thing 2018-08-04 09:47:29 -07:00
Sealable.h Fabric: Making Sealable debug-only thing 2018-08-04 09:47:29 -07:00