Permalink
Browse files
docs(ngMock/$exceptionHandler): fix formatting
Too much indentation, made text get formatted as code block.
- Loading branch information
Showing
with
6 additions
and
6 deletions.
-
+6
−6
src/ngMock/angular-mocks.js
|
|
@@ -220,13 +220,13 @@ angular.mock.$ExceptionHandlerProvider = function() { |
|
|
* @param {string} mode Mode of operation, defaults to `rethrow`. |
|
|
* |
|
|
* - `log`: Sometimes it is desirable to test that an error is thrown, for this case the `log` |
|
|
* mode stores an array of errors in `$exceptionHandler.errors`, to allow later |
|
|
* assertion of them. See {@link ngMock.$log#assertEmpty assertEmpty()} and |
|
|
* {@link ngMock.$log#reset reset()} |
|
|
* mode stores an array of errors in `$exceptionHandler.errors`, to allow later assertion of |
|
|
* them. See {@link ngMock.$log#assertEmpty assertEmpty()} and |
|
|
* {@link ngMock.$log#reset reset()}. |
|
|
* - `rethrow`: If any errors are passed to the handler in tests, it typically means that there |
|
|
* is a bug in the application or test, so this mock will make these tests fail. |
|
|
* For any implementations that expect exceptions to be thrown, the `rethrow` mode |
|
|
* will also maintain a log of thrown errors. |
|
|
* is a bug in the application or test, so this mock will make these tests fail. For any |
|
|
* implementations that expect exceptions to be thrown, the `rethrow` mode will also maintain |
|
|
* a log of thrown errors in `$exceptionHandler.errors`. |
|
|
*/ |
|
|
this.mode = function(mode) { |
|
|
|
|
|
|