Piping through to a new stream
- Dominant language
- JavaScript
- Stars
- 3.4k
- Forks
- 145
- PR merge metrics
- No merged PRs in 30d
Description
First of all, awesome library you have built!
I'm trying to wrap my head around a few things, and currently looking at being able to setup a stream, and then pipe the data from the stream into another (which may go through X number of other streams).
These streams would further filter, or do some magic, run some async code etc.
What's the best way to do this?
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by reviewing Highland's existing stream and pipe documentation and API examples, then determine whether the requested chaining and asynchronous processing are already supported. Done would require a clearly defined behavior and an agreed implementation or documentation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- stream-processing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100