max-mapper / max-mapper/socket-sync
split websocket upgrade stuff out into its own module
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
the websocket upgrade + session checking code needs to become its own module with a well defined API for checking a session and calling a callback with the upgraded socket
cc @nhq
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
Start by locating the websocket upgrade and session-checking code in the repository and trace how upgraded sockets are currently handled. Define the module boundary and API around session checking and the callback for the upgraded socket, then verify that existing replication behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authentication, backend, networking
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100