microsoft / microsoft/react-native-windows
DevSupportManager is a singleton - but it shouldn't be
Open
Nobody has claimed this yet.
Area: Debug Infrastructure
bug
Workstream: Developer Experience
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
If you had multiple instances trying to run in debug mode within a single app, they would try to share the same DevSupportManager, and hit issues.
Contributor guide
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
Start by locating DevSupportManager and tracing how its singleton instance is created and accessed. Inspect the callers and any related tests; done means separate debug-mode instances can coexist within one app without sharing the same manager.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native
- Domain
- devtools, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100