No description provided.
Added a configuration option for setting path to notifier.js (Default…
@duncanbeevers What are your thoughts on this / moving forwards as we update the javascripit app?
The way the JS notifier is written, it's well decoupled from the whatever app its used in. Specifically, the notifier reports directly to the Airbrake API servers via a JSONP GET, avoiding cross-origin request restrictions.
Explicitly specifying the load path but not providing control of the loading mechanism (async download via document.write) sort of conflates the loading with the functionality of the script itself.
In short, I like the knobs, but I think they're on the wrong box.
@duncanbeevers cool, thanks for the clarification.
@vpuzzella please refer to https://github.com/airbrake/airbrake-js for further changes.