[
https://issues.apache.org/jira/browse/CB-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266096#comment-13266096
]
Patrick Mueller commented on CB-611:
------------------------------------
Can you be more precise with "keep the console logging in one place"?
I assume you mean, "keep all the console-related methods in a single object -
the {{console}} object".
Meaning, bolt on new methods to a pre-existing object that we don't necessarily
have control over.
aka "money patch": http://en.wikipedia.org/wiki/Monkey_patch
I'd also like to understand the use case here. You mention it being for a
plugin you've written. Is this logging exposed to users of the plugin, or just
folks developing the plugin?
> Logging levels
> --------------
>
> Key: CB-611
> URL: https://issues.apache.org/jira/browse/CB-611
> Project: Apache Callback
> Issue Type: Improvement
> Components: iOS
> Affects Versions: Master
> Environment: Run Cordova/PhoneGap with Cordova-SQLitePlugin and some
> other plugins
> Reporter: Chris Brody
> Assignee: Shazron Abdullah
> Fix For: Master
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> I got a pull request on my Cordova-SQLitePlugin with a special logging
> function that is only logging when built as a debug version. I believe this
> issue should be solved in the core with a log function that is only logging
> when built as a debug version. Ideally a logging facility with multiple log
> levels. Please forgive me if this has already been done somewhere.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
