- From: Kyle Simpson <notifications@github.com>
- Date: Wed, 25 Jan 2017 04:51:02 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 25 January 2017 12:51:55 UTC
Is it absolutely unacceptable to change the return type of `fetch(..)`? I don't mean the "adding methods to the promise" stuff, I mean literally changing `fetch(..)` to return something that's not a promise. Yes, I know this will break code. I'm just asking if it's possible to consider that?
I don't suspect this will considered at this late point, but I figured I'd just ask.
------
I had suggested in that other "fetch cancelation" thread that `fetch()` return the fetch-controller, and that this fetch-controller object have a property on it for the promise that's currently the return of `fetch(..)`, as well as the `abort()` method:
```js
let { abort, pr } = fetch(..);
```
The ergonomics of using `fetch()` only for the promise just requires an extra `.pr` in there, like:
```js
await fetch(..).pr
```
-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/447#issuecomment-275100281
Received on Wednesday, 25 January 2017 12:51:55 UTC