microsoft / microsoft/react-native-windows-samples
Document E2E Debug Experience
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 544
- Forks
- 218
- PR merge metrics
- No merged PRs in 30d
Description
Meta-point for triage: we don't talk about the e2e debug experience in our docs but we should; there are Windows-specific pieces (e.g. how to use VS, does flipper work, JS engine choice) as well as RN concepts that the main RN website doesn't go into enough detail either (web debugging vs. direct debugging).
Originally posted by @asklar in https://github.com/microsoft/react-native-windows/issues/7615#issuecomment-824665183
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 documentation file or test is named. Start by locating the repository’s existing E2E and debugging documentation, then compare coverage for Windows-specific VS usage, Flipper support, JavaScript engine choice, and web versus direct debugging. Done means these topics are documented clearly enough for users to follow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100