🛠️ Support Fabric components that are interfaceOnly: true

[sidorchukandrew]

There are some components where the developer will need to provide custom C++ classes (like shadow nodes and measurements managers). I have not come across a standard way of organizing those files, but it would be immensely helpful for this library to support templating this out. I did a global search on GitHub to locate any library that uses react-native-builder-bob and has custom C++ files and had very limited results. I did come across react-native-live-markdown.

There are other examples of components that use custom C++ classes but don't use react-native-builder-bob:

• https://github.com/callstack/react-native-slider
• https://github.com/react-native-progress-view/progress-view
• https://github.com/react-native-picker/picker

I did end up publishing https://github.com/rn-nui/switch using react-nativ-builder-bob so this could also be used as a starting point.

I'm not saying that a maintainer must add this feature, but I am looking to see if this is even something the maintainers would want in this library.

[sidorchukandrew]

I made a major breakthrough with this today. Your library needs to have a react-native.config.js file specific to the library, separate from the example app's react-native.config.js. This is how React Native knows where to copy your CMakeLists file from and your component descriptor for Android.

[sidorchukandrew]

Also, the package.json needs to export react-native. It needs to point at your ./src/index.ts(x)

[satya164]

Would you like to make a PR to add it to our docs?