tiny-devs / tiny-devs/tiny-dungeon-online
Optimize common messages
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 64
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
The method "unicastMessage" (server\clientHandler.ts) is used for a couple of things, like dialogs. Another use is for error or warning messages. We could optimize the data transferring of those messages, placing them on the client and just sending their "id" from the server (and not the full message)
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 in server\clientHandler.ts at unicastMessage, then trace its dialog and error/warning call sites and the corresponding client-side message handling. Determine where common messages can be identified by an id without changing their visible behavior; done means those messages transfer by id and the affected dialogs and warnings still work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- deno, typescript
- Domain
- full-stack, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100