Re: [whatwg/fetch] Editorial: Add prose about constructing a request (PR #1585)

@jyasskin commented on this pull request.



> @@ -8380,6 +8380,56 @@ correctly. This section aims to give some advice.
 
 <p class=XXX>This is a work in progress.
 
+<h3 id=fetch-elsewhere-request>Constructing a request</h3>

I think that subsequent section could use an example of how to use it. I think a lot of people expect to be able to say: 
1. In parallel:
   1. fetch the request.
   2. Wait for the fetch to finish.
   3. Use the response.

And with the setup of the *processResponse* algorithms, that just doesn't work. You have to do something more like

1. Fetch the request, with the following algorithms as arguments:
   <dl><dt>processResponse<dd>Steps
   <dt>processResponseConsumeBody<dd>Other Steps

It might also be helpful to rewrite that section to map from a spec's goals about how it'll handle the response, to the set of algorithm arguments it ought to pass.

But +100 for doing all that in a separate PR. Writing this section is a great first step.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/1585#discussion_r1061147052
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/pull/1585/review/1235366465@github.com>