Re: [whatwg/fetch] History behind the decision to make fetch return a Promise (#611)

https://github.com/whatwg/fetch/commit/2e82a88634f0cd23de1977b11b36d1e907d01f5c was the commit where it got added to Fetch (note that Fetch is much more than the API, but I'm assuming by "this spec" you mean the API).

https://github.com/w3c/ServiceWorker/commits/master/controller.ts has some early history in the service worker repository.

Looking through IM conversations @wycats further refined the shape of the API. (And I should probably add him to the acknowledgments section!)

It also got discussed and further changed based upon mailing list discussion: https://lists.w3.org/Archives/Public/public-whatwg-archive/2014Jun/ (search for "fetch").

There's also some archived IRC discussion at: http://logs.glob.uno/?c=freenode%23whatwg&s=15+May+2014&e=8+Jun+2014.

Looking through the material I think we also thought it would be much more common to subclass promise than it turned out to be.

I'll leave this open for a bit, perhaps @slightlyoff, @jakearchibald, @wycats, and others can add their anecdotes. Would be interesting.

-- 
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/611#issuecomment-333176610