-
Notifications
You must be signed in to change notification settings - Fork 132
wip injectable stream #408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev-1.0
Are you sure you want to change the base?
Conversation
|
]); | ||
} | ||
|
||
get readable() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we also consider supporting "eject" (read single value from stream) operation? Basically making stream also have a queue-like API with put
as inject
and get
as eject
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure if there's a concrete use case?
I'd be in favor of implementing additional features (generally) only once we know we have a defined use case for it.
} | ||
} | ||
|
||
async close() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@toubatbrian might be worth taking over this PR and working on the releasing the lock on the readable source once we close the stream.
Some tests would be good to.
@@ -2,6 +2,7 @@ | |||
"extends": "../tsconfig.json", | |||
|
|||
"compilerOptions": { | |||
"types": ["node"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
instead of defining it here, I think it would make sense to define it in the root package.json so that all packages (including plugins) get it by default
No description provided.