Refactor read operation algorithm
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 118
- Forks
- 52
- Avg merge
- 9d 16h
- Merged PRs (30d)
- 1
Description
The read operation algorithm uses the inappropriate "in parallel" concept(see event-loop-for-spec-authors), and instead of rewording this, it could be simplified through the use ofreadablestreamdefaultreader-read-all-bytes.
Here is an example from Fetch.
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 with the linked File API read operation algorithm, then read the Streams specification's readablestreamdefaultreader-read-all-bytes definition and Fetch's body-fully-read example. Compare their handling of the read operation and event-loop wording; done means the File API algorithm is simplified consistently with those references.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation, web-dev
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100