`catch` missing when blessed about fireproof HOT 1 CLOSED

The promises returned by Fireproof in the bless case are Promises/A+
compliant, not ES6 compliant (https://promisesaplus.com). In general what
we need is to refactor the entire codebase to use native Promise calls and
clean things up that way. But going forward .bless is deprecated together
with the whole "defer" model, which is not ES6 either.

On Tue, Dec 15, 2015 at 11:19 AM Josh Dague [email protected]
wrote:

When blessed, the thing returned from Fireproof is not an actual promise,
just an object with a then that is bound to the blessed library's then
function. The object is missing the catch method required by ES6 §
25.4.5.1
http://www.ecma-international.org/ecma-262/6.0/#sec-promise.prototype.catch
.

Ideally, Fireproof would return a real promise from the blessed library.
(When un-blessed -- ie using native promises -- it does appear to return
real promises.)

I'm pretty sure this is new to 3.1.

—
Reply to this email directly or view it on GitHub
#22.

from fireproof.