Re: [whatwg/fetch] Ensure that a Request object can be used as RequestInit (Issue #1486)

> And I guess one way to read this is as a request to expose duplex on `Request`.

Yes. Or more precisely to update this type:
```
constructor(RequestInfo input, optional RequestInit init = {});
 ```
 to be:
 ```
 constructor(RequestInfo input, optional (Request or RequestInit) init = {});
 ```
 https://fetch.spec.whatwg.org/#request-class
 
 In other words, User-Agents should expect a `Request` as either the first parameter, the second, or both.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1486#issuecomment-1253676242
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/1486/1253676242@github.com>