LibWeb/Streams: Actually implement the piped through steps

This mistakenly implemented the 'piped to' operation on ReadableStream.
No functional difference as the caller was doing the extra work already
of 'piped through' vs 'piped to'.
This commit is contained in:
Shannon Booth 2024-12-26 12:02:07 +13:00 committed by Tim Flynn
commit ffda698d3a
Notes: github-actions[bot] 2024-12-27 14:57:36 +00:00
3 changed files with 14 additions and 9 deletions

View file

@ -109,7 +109,7 @@ public:
WebIDL::ExceptionOr<void> pull_from_bytes(ByteBuffer);
WebIDL::ExceptionOr<void> enqueue(JS::Value chunk);
void set_up_with_byte_reading_support(GC::Ptr<PullAlgorithm> = {}, GC::Ptr<CancelAlgorithm> = {}, double high_water_mark = 0);
GC::Ref<WebIDL::Promise> piped_through(GC::Ref<WritableStream>, bool prevent_close = false, bool prevent_abort = false, bool prevent_cancel = false, JS::Value signal = JS::js_undefined());
GC::Ref<ReadableStream> piped_through(GC::Ref<TransformStream>, bool prevent_close = false, bool prevent_abort = false, bool prevent_cancel = false, JS::Value signal = JS::js_undefined());
GC::Ptr<WebIDL::ArrayBufferView> current_byob_request_view();