You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/the-new-architecture/backward-compatibility-fabric-components.md
+86-3Lines changed: 86 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -287,7 +287,7 @@ my-component
287
287
│ │ ├── AndroidManifest.xml
288
288
│ │ └── java
289
289
│ │ └── com
290
-
│ │ └── MyComponent
290
+
│ │ └── mycomponent
291
291
│ │ ├── MyComponentView.java
292
292
│ │ ├── MyComponentViewManagerImpl.java
293
293
│ │ └── MyComponentViewPackage.java
@@ -306,8 +306,12 @@ my-component
306
306
307
307
The code that should go in the `MyComponentViewManagerImpl.java` and that can be shared between the Native Component and the Fabric Native Component is, for example:
// static custom function from the shared implementation
480
+
MyComponentViewManagerImpl.setFoo(view, param);
481
+
}
482
+
}
483
+
```
484
+
485
+
</TabItem>
486
+
</Tabs>
487
+
405
488
For a step-by-step example on how to achieve this, have a look at [this repo](https://github.com/react-native-community/RNNewArchitectureLibraries/tree/feat/back-fabric-comp).
For a step-by-step example on how to achieve this, have a look at [this repo](https://github.com/react-native-community/RNNewArchitectureLibraries/tree/feat/back-turbomodule).
0 commit comments