3 ms·
Unfortunately Promises need to be fixed before fetch will be sane and here's how the promises spec currently looks: - unhandled errors silently swallowed [1] (
by nilliams 10y ago
Unfortunately Promises need to be fixed before fetch will be sane and here's how the promises spec currently looks:
- unhandled errors silently swallowed [1] (this is the case for the most popular polyfill [1] too - the one recommended by fetch polyfills, BEWARE [3])
- no 'finally' method, despite pretty much everything in a UI needing some common 'cleanup' after e.g. a fetch()
- not cancellable
Right now you're better off with `$.ajax` (maybe make a custom build of jQuery) or a promise-like library like reqwest [2], rather than fighting with fetch.
[1] https://github.com/stefanpenner/es6-promise/issues/70#issuecomment-223898502 https://github.com/stefanpenner/es6-promise/issues/70#issuec...
[2] https://github.com/ded/reqwest https://github.com/ded/reqwest
[3] http://requirebin.com/?gist=8f13d5147c1c252ab1691115bfa8b7c5 http://requirebin.com/?gist=8f13d5147c1c252ab1691115bfa8b7c5
- k__ 10y agoI don't know why they pushing Observables AND Promises in ECMAScript. Observables a much more flexible and don't have these problems :/