microsoft / microsoft/react-native-windows
Move IPC Reconnect Loop From API user to node-rnw-rpc (automation-channel)
Open
Nobody has claimed this yet.
enhancement
Workstream: ES Compliance SFI
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
We currently expose a single connection to clients, leading them to reimplement server loop. We should expose the loop directly with cancellationToken capability to interrupt.
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 the node-rnw-rpc entry point and the current API-user IPC connection loop for the automation-channel. Trace how reconnects are handled and where cancellationToken can interrupt the loop. Done means clients can use the exposed reconnect loop directly without reimplementing the server loop, with cancellation supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, node.js, react-native
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100