Create API variants for websockets that accept Source or Sink
Open
1 - triaged
help wanted
small
t:routing
- Dominant language
- Scala
- Stars
- 1.4k
- Forks
- 584
- Avg merge
- 14h 33m
- Merged PRs (30d)
- 24
Description
Many people want just one-directional communcation, so they have a Sink or Source, we should give them helper APIs to be able to use them without hassle.
Contributor guide
Research direction
No files, tests, or entry points are named. Start by locating the websocket API definitions and existing Source- and Sink-based stream handling, then determine the intended helper variants. Done means one-directional users can use the websocket APIs directly with either a Source or a Sink, with coverage for the new entry points.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100