microsoft / microsoft/react-native-windows-samples
Create guide for adding macOS support to an existing community module
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 544
- Forks
- 218
- PR merge metrics
- No merged PRs in 30d
Description
Typically the engineering here is lower than say a Windows module because the iOS code can be leveraged. The higher cost is knowing what to do, and going through the PR process. We should document that to help external contributors to help out here.
Of note we need this for Windows too... I know there was some discussion/issue on that, but I couldn't find it.
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 file or test is named. Start by reviewing how an existing iOS-backed community module is structured and the repository's contribution and PR process; done means a guide that explains the steps for adding macOS support and contributing the change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, macos, react-native
- Domain
- documentation, mobile-dev
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100