[
https://issues.apache.org/jira/browse/CB-9366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136390#comment-15136390
]
ASF GitHub Bot commented on CB-9366:
------------------------------------
Github user jimmont commented on the pull request:
https://github.com/apache/cordova-js/pull/118#issuecomment-181090801
@nikhilkh Yes. Throwing errors is a reliable way of both debugging and
finding problems. When they're intercepted I can't do that as easily. (Similar
is true of `cordova-plugin-console`.) In looking through the source cordova
uses a module loader and http requests to setup **global** APIs from the
**local filesystems** on the device, and various events/event-system to get the
sequence and setup right. Seems sub-optimal to me. (For example, a concatenated
script which works with the global namespace directly seems like the simple
approach, all things considered, and is what happens in the end anyway.) But I
haven't finished looking at all the contemporary platforms (that I want to
target anyhow). No one asked for these observations but given I'm seeing them,
and how expensive time-wise it is to work either with or around them, thought
I'd mention it. (In case more context is helpful: imagine debugging getting
cordova and all the desired plugins working in a worker so the UI is more
responsive. By all appearances the original authors didn't plan for this
scenario.)
> Log error.stack when a call to a plugin throws an exception
> -----------------------------------------------------------
>
> Key: CB-9366
> URL: https://issues.apache.org/jira/browse/CB-9366
> Project: Apache Cordova
> Issue Type: Improvement
> Components: CordovaJS
> Affects Versions: Master
> Reporter: Nikhil Khandelwal
> Assignee: Nikhil Khandelwal
> Priority: Minor
>
> This can help in isolating the cause of the error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
