Function signature change: reading all bytes from a stream
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 118
- Forks
- 52
- Avg merge
- 9d 16h
- Merged PRs (30d)
- 1
Description
The signature of reading all bytes had changed:
https://github.com/whatwg/streams/pull/1250
It now accepts successSteps and failureSteps instead of returning a Promise, in an attempt to decouple streams from JS when appropriate.
Opening this issue since this spec uses that function
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the File API specification by locating its use of the Streams “reading all bytes” function, then compare that invocation with the linked Streams change. Update the specification to use the new successSteps and failureSteps signature, and verify that no promise-based wording remains for this function.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100