Proposed fix for Issue #7

[BITespresso]

I'd like to propose this as fix for Issue https://github.com/bluejava/zousan/issues/7

It will add these changes:

• Throw a TypeError if the constructor is called without new
• Catch errors in the Zousan resolver function
• Throw a TypeError if the constructor is called with an argument that is not a function
• Suppress the 'uncaught rejection' error message if the rejection happens in the constructor or in the class function Zousan.resolve

[watnab]

Google Chrome 71.0.3578.98(Official Build)(Windows 10/64 bit)

Original Zousan(v2.3.3)

var o = new Zousan(function () { throw 123; }); results:

Uncaught 123 //highlighted as error

o results:

undefined

rejectWithErrorSuppression( 3098a55 )

var s = new Zousan(function () { throw 123; }); results:

undefined

s.catch(console.log), void 0 results:

123
undefined

Native Promise

var n = new Promise(function () { throw 123; }); results:

undefined
Uncaught (in promise) 123 //highlighted as error

n.catch(console.log), void 0 results:

123
undefined

---

• 3098a55 makes Zousan can catch the error thrown in the constructor.
• However it may be better the error is reported when the rejection is not caught yet.

[BITespresso]

@watnab Thanks for the summary!

See my thoughts in: https://github.com/bluejava/zousan/issues/7#issuecomment-449978770

BTW: Notice that Chrome Browser removes the

Uncaught (in promise) 123 //highlighted as error

once you execute n.catch(console.log), void 0.

[watnab]

BTW: Notice that Chrome Browser removes

Yes, the console output in Chrome may be something living.