-
Notifications
You must be signed in to change notification settings - Fork 165
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
Add piping helpers for other specs #1113
Conversation
Woah, I totally missed this. Sorry. |
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.
lgtm with nits.
index.bs
Outdated
|
||
<div algorithm="ReadableStream pipe through"> | ||
The result of a {{ReadableStream}} |readable| <dfn export for="ReadableStream" lt="pipe | ||
through|piping through">piped through</dfn> a {{TransformStream}} |transform|, given an optional |
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.
Question: do we want to require a {{TransformStream}}
, or would the [=transform stream=]
concept be sufficient here?
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.
The latter would require doing JavaScript-observable Get()s, which introduces the possibility of sync exceptions. I think we should leave it as just TransformStream
for now unless some spec comes along that needs the generic concept.
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.
That's reasonable.
Given that you found several good nits last round and I just got my eyes dilated so can barely see what I'm typing, I'd appreciate another once-over from you before merging :) |
I took another look. Still lgtm! |
See whatwg/fetch#1199.
Preview | Diff