poelstra ts-stream issues

poelstra / ts-stream

Type-safe object streams with seamless support for backpressure, ending, and error handling

MIT License

65 stars 13 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Generic Splitter

#18 rogierschouten opened 9 years ago
0
Generic Node.JS stream wrapper

#17 rogierschouten closed 7 years ago
4
Stream#from() does not end the stream on abort()

#16 rogierschouten closed 9 years ago
11
ReadableStream#map does not have all arguments of Stream#map

#15 rogierschouten closed 9 years ago
1
Add aborter callback to forEach()

#14 poelstra closed 9 years ago
3
Aborting twice should be possible

#13 rogierschouten closed 9 years ago
2
isEnded() should already be true when end() is sent, not when end() is resolved

#12 rogierschouten closed 9 years ago
5
Cosmetics: please return the stream from forEach() to facilitate nicer-looking code

#11 rogierschouten closed 9 years ago
2
Allow passing `null` to `end()`

#10 poelstra closed 9 years ago
0
Consider optional 'ender' callback to map(), filter(), etc

#9 poelstra closed 9 years ago
1
Consider wrapping error passed to abort() in AbortError

#8 poelstra closed 9 years ago
4
Please connect the ended() promises of connected streams

#7 rogierschouten closed 9 years ago
5
Please don't send end() when abort() is called

#6 rogierschouten closed 9 years ago
5
Unexpected WriteAfterEndError after swallowing write error from map function

#5 rogierschouten closed 9 years ago
1
Please incorporate .ts files into published NPM module

#4 rogierschouten closed 9 years ago
1
Please add public isEnded(): boolean

#3 rogierschouten closed 9 years ago
1
Return a promise from Readable.forEach()

#2 rogierschouten closed 9 years ago
2
.map() should be on Readable interface

#1 rogierschouten closed 9 years ago
2