search

microsoft / react-native-windows-samples

A repository showcasing React Native samples and templates for Windows, macOS, and Surface Duo.
https://microsoft.github.io/react-native-windows/
MIT License
486 stars 201 forks source link

Document best practices for native side of app to communicate with native module #407

Open asklar opened 3 years ago

asklar commented 3 years ago

Autolinking will create a ReactPackageProvider for every linked module. However the native side of the app doesn't have a way to access the [native] instance of the native module to negotiate or communicate properties/call APIs.

Workaround: static APIs/properties It would be good to provide a mechanism to avoid this.

NickGerleman commented 3 years ago

Apart from the PropertyBag which you mentioned, ReactNotificationService can also help address this.

chrisglein commented 3 years ago

Do we build a mechanism for this or do we just document best/available practices for how to set up this kind of communication? Are there existing samples we can point to that use ReactNotificationService or the PropertyBag that developers can use as a template? We really don't want people to try to invent their own static pattern and get the instancing wrong, so this is a good candidate for documentation.

asklar commented 3 years ago

Related to: #333 and #198