microsoft / microsoft/react-native-windows-samples
Document best practices for native side of app to communicate with native module
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 544
- Forks
- 218
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by tracing how autolinking creates a ReactPackageProvider for each linked module and how the native app currently accesses module instances. Done should include a defined communication mechanism and guidance that replaces the static API/property workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100