From 666705c0a4d128fdaa0a53929c194232a4e34087 Mon Sep 17 00:00:00 2001
From: Jared Forsyth
Date: Fri, 30 Aug 2013 10:47:55 -0600
Subject: docs($exceptionHandler): add an example of overriding the handler

Closes #3816
---
 src/ng/exceptionHandler.js | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

(limited to 'src/ng/exceptionHandler.js')

diff --git a/src/ng/exceptionHandler.js b/src/ng/exceptionHandler.js
index 2adc3f17..c3795bb7 100644
--- a/src/ng/exceptionHandler.js
+++ b/src/ng/exceptionHandler.js
@@ -9,10 +9,24 @@
  * Any uncaught exception in angular expressions is delegated to this service.
  * The default implementation simply delegates to `$log.error` which logs it into
  * the browser console.
- *
+ * 
  * In unit tests, if `angular-mocks.js` is loaded, this service is overridden by
  * {@link ngMock.$exceptionHandler mock $exceptionHandler} which aids in testing.
  *
+ * ## Example:
+ * 
+ * <pre>
+ *   angular.module('exceptionOverride', []).factory('$exceptionHandler', function () {
+ *     return function (exception, cause) {
+ *       exception.message += ' (caused by "' + cause + '")';
+ *       throw exception;
+ *     };
+ *   });
+ * </pre>
+ * 
+ * This example will override the normal action of `$exceptionHandler`, to make angular
+ * exceptions fail hard when they happen, instead of just logging to the console.
+ *
  * @param {Error} exception Exception associated with the error.
  * @param {string=} cause optional information about the context in which
  *       the error was thrown.
-- 
cgit v1.2.3