Optimization for coding with pub-sub pattern
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 69
- Forks
- 59
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 26
Description
Pub-Sub Pattern
broadcast "foo", data
onMsg "foo", data => {
// ...
}
Optimizations
- Go to listener / broadcaster
- Type safety: check message name & data
- Update APIs (
broadcast&onMsg) - UI decorations like resource-reference
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 listener and broadcaster implementation and the existing broadcast and onMsg APIs. Define completion around type-checking message names and data, updated APIs, and the requested UI decorations such as resource references.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100