MobileAppTracking/fn-logger — pull request #11 by joshschumacher (2014-01-15 00:35:12+00:00)
Title: Log formatting cleanup

- Better handling of newlines
- When using $log with a jQuery message, display a truncated version of the $.text() in console
- When displaying Error messages in debugger, place full stack trace in additional data area and short message as the primary log message
- Give a few previously anonymous functions names so they produce more readable stack traces

Attempted to fix #7 but determined it’s not possible to make stack traces really awesome. The stack traces that need to be improved are auto-generated by the browser with a console.error() call; there isn’t a way to pass a custom stack trace to a console.error() call. Could possibly fake the call and do a console.log with css formatting but it wouldn’t be filtered by the browser as an error which could cause confusion. Did some formatting work to improve the experience around reporting stack traces in the logger.