Repository navigation
Integration with Ember.Logger? #7
Description
Activity
The consensus seems to be that
Ember.Loggerisn't really necessary anymore, since it's basically just a polyfill forconsole.log. It intentionally didn't get assigned an import path in the new modules API.The
debuglibrary itself supports custom output streams and custom formatters, though, so you could do something like this:window.debug.log = (...params) => { // multiplex to various locations, including Ember.Logger.debug if you like };
Q: How difficult would it be to use
Ember.Logger.debuginstead ofthis.debug? Have not overwritten Ember core components before, and was hoping for a bit of guidance within the context ofember-debug-logger, possibly for a PR.My issue with
this.debugis the difficulty of refactoring/adding additional functionality beyond the scope ofember-debug-logger. For example, while console logging is great for now, I know I'll want to injest JSON-formatted log files, either to a 1st-party logging end-point I create or a 3rd-party service (AWS CloudWatch, Airbrake, Rollbar, etc.)If
this.debugwere wrapped inEmber.Logger.debug, I could include these additional log streams atEmber.Logger.debugwithout touchingember-debug-logger.There is precedent in the community. For example,
ember-cli-rollbarrollbar.critical(msg) <--> Ember.Logger.error(msg), see: https://github.com/davewasmer/ember-cli-rollbar/blob/master/app/initializers/rollbar.js#L8