e581977b51
Summary: The whole mounting iOS infra now uses `ComponentHandle` instead of `std::string` as a reference to particular `ComponentView` implementation. All changes are pretty straightforward, we use a different thing/type to refer to the particular class; no changes in the logic besides a new `RCTComponentViewFactory` that serves the same role of classes registry as Objective-C runtime served previously. That has several benefits: * It should be slightly faster, mostly because we don't need to convert `char *` strings to `std::string` and then to `NSString *`. * We don't need string-based component-name maps anymore (at least on this layer). We can call classes as we want and it will work because of classes are now explicit about which ShadowNodes they are compatible with. * Most importantly, it's explicit now! That means that no runtime magic is involved anymore and we can rely on static linting tool now and not be afraid of improper code stripping/overoptimization. Reviewed By: mdvacca Differential Revision: D13130760 fbshipit-source-id: aadf70525a1335b96992443abae4da359efdc829 |
||
|---|---|---|
| .. | ||
| Base | ||
| CxxBridge | ||
| CxxModule | ||
| CxxUtils | ||
| DevSupport | ||
| Fabric | ||
| Inspector | ||
| Modules | ||
| Profiler | ||
| React.xcodeproj | ||
| UIUtils | ||
| Views | ||
| .clang-format | ||
| third-party.xcconfig | ||