jsb.onError design issues about cocos-engine HOT 4 OPEN

jsb is replaced with native, I think we need to put onError to native namespace.

Yes, jsb.onError capture all errors which is not as standard as which in web and nodejs.

https://developer.mozilla.org/en-US/docs/Web/API/Window/unhandledrejection_event
https://www.geeksforgeeks.org/node-js-process-unhandledpromiserejection-event/

Promise unhandled rejection should be captured by a separate callback.

from cocos-engine.

jsb is replaced with native, I think we need to put onError to native namespace.

Yes, jsb.onError capture all errors which is not as standard as which in web and nodejs.

https://developer.mozilla.org/en-US/docs/Web/API/Window/unhandledrejection_event https://www.geeksforgeeks.org/node-js-process-unhandledpromiserejection-event/

Promise unhandled rejection should be captured by a separate callback.

I don't have the same idea as you. I think it should be placed in an interface like sys.on("error") to adapt to all platforms, so that users can use this interface across platforms.

from cocos-engine.

Because if users want to catch errors, no one wants to only take effect on the native side, so they have to adapt themselves.

from cocos-engine.

Agree. It seems sys.on('error', function() {...}) be a better choise.

from cocos-engine.