WebSocketSubject may have different input and output types.
Open
Nobody has claimed this yet.
bug
help wanted
- Dominant language
- TypeScript
- Stars
- 31.7k
- Forks
- 3k
- PR merge metrics
- No merged PRs in 30d
Description
Just what the title says... The AnonymousSubject (aka "frankensubject") probably also needs some typings love.
Basically, a nicer interface would be:
class WebSocketSubject<In, Out> extends Observable<Out> implements Observer<In> {
// ...stuff
}
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 with the WebSocketSubject and AnonymousSubject entry points and inspect their current TypeScript typings. Confirm that WebSocketSubject can express separate input and output types, then verify that the corresponding public typings and existing type checks cover the intended interfaces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100