Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447)

> Is it absolutely unacceptable to change the return type of fetch(..)?

Not at all, we can avoid breaking code and just return an object which is a promise that has a `cancel` method but no chaining at all (so the capability can be further separated). In my view, this is similar to your idea except the object returned also has a `then`. 

The consensus in the meeting was that since controller is a very unobtrusive API - it will give people the capability to cancel `fetch` requests but does not really limit exploring other options (like tokens, or cancellable promises) in the future. 

The consensus was basically to go ahead with the controller option and to observe how people interact with it - if people start wrapping `fetch` and adding `.cancel` on it - the spec can be amended to add `.cancel` in an ad-hoc way. A controller also means finer grained control than just a `.cancel`. 

-- 
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-275105241