Merge pull request ember-learn#319 from ember-learn/locks-patch-7

Update debugging.md

Author: acorncom

guides/release/configuring-ember/debugging.md

@@ -3,7 +3,7 @@ with your application.
 
 ## Routing
 
-#### Log router transitions
+### Log router transitions
 
 ```javascript {data-filename=app/app.js}
 import Application from '@ember/application';
@@ -21,41 +21,37 @@ export default Application.extend({
 ```
 ## Views / Templates
 
-#### Log view lookups
+### Log view lookups
 
 ```javascript {data-filename=config/environment.js}
 ENV.APP.LOG_VIEW_LOOKUPS = true;
 ```
-#### View all registered templates
-```javascript
-Ember.keys(Ember.TEMPLATES)
-```
 
 ## Controllers
 
-#### Log generated controller
+### Log generated controller
 
 ```javascript {data-filename=config/environment.js}
 ENV.APP.LOG_ACTIVE_GENERATION = true;
 ```
 
 ## Observers / Binding
 
-#### See all observers for an object, key
+### See all observers for an object, key
 
 ```javascript
 Ember.observersFor(comments, keyName);
 ```
 
-#### Log object bindings
+### Log object bindings
 
 ```javascript {data-filename=config/environments.js}
 ENV.APP.LOG_BINDINGS = true;
 ```
 
 ## Miscellaneous
 
-#### Turn on resolver resolution logging
+### Turn on resolver resolution logging
 
 This option logs all the lookups that are done to the console. Custom objects
 you've created yourself have a tick, and Ember generated ones don't.
@@ -70,15 +66,14 @@ export default Application.extend({
   LOG_RESOLVER: true
 });
 ```
-#### Dealing with deprecations
+### Dealing with deprecations
 
 ```javascript
 Ember.ENV.RAISE_ON_DEPRECATION = true;
 Ember.ENV.LOG_STACKTRACE_ON_DEPRECATION = true;
 ```
 
-
-#### Implement an Ember.onerror hook to log all errors in production
+### Implement an Ember.onerror hook to log all errors in production
 
 ```javascript
 Ember.onerror = function(error) {
@@ -92,7 +87,7 @@ Ember.onerror = function(error) {
 }
 ```
 
-#### Import the console
+### Import the console
 
 If you are using imports with Ember, be sure to import the console:
 
@@ -106,28 +101,7 @@ Ember = {
 };
 ```
 
-#### Errors within an `RSVP.Promise`
-
-There are times when dealing with promises that it seems like any errors
-are being 'swallowed', and not properly raised. This makes it extremely
-difficult to track down where a given issue is coming from. Thankfully,
-`RSVP` has a solution for this problem built in.
-
-You can provide an `onerror` function that will be called with the error
-details if any errors occur within your promise. This function can be anything,
-but a common practice is to call `console.assert` to dump the error to the
-console.
-
-```javascript {data-filename=app/app.js}
-import { assert } from '@ember/debug';
-import RSVP from 'rsvp';
-
-RSVP.on('error', function(error) {
-  assert(error, false);
-});
-```
-
-#### Errors within `Ember.run.later` Backburner
+### Errors within `Ember.run.later` Backburner
 
 [Backburner.js](https://github.com/ebryn/backburner.js) has support for stitching the stacktraces together so that you can
 track down where an error thrown by `Ember.run.later` is being initiated from. Unfortunately,

guides/v1.10.0/understanding-ember/debugging.md

@@ -9,12 +9,12 @@ to inspect Ember objects in your application.
 
 ## Routing
 
-#### Log router transitions
+### Log router transitions
 
 ```javascript
 window.App = Ember.Application.create({
   // Basic logging, e.g. "Transitioned into 'post'"
-  LOG_TRANSITIONS: true, 
+  LOG_TRANSITIONS: true,
 
   // Extremely detailed logging, highlighting every internal
   // step made while transitioning into a route, including
@@ -24,19 +24,19 @@ window.App = Ember.Application.create({
 });
 ```
 
-#### View all registered routes
+### View all registered routes
 
 ```javascript
 Ember.keys(App.Router.router.recognizer.names)
 ```
 
-####  Get current route name / path
+###  Get current route name / path
 
 Ember installs the current route name and path on your
 app's `ApplicationController` as the properties
 `currentRouteName` and `currentPath`. `currentRouteName`'s
-value (e.g. `"comments.edit"`) can be used as the destination parameter of 
-`transitionTo` and the `{{linkTo}}` Handlebars helper, while 
+value (e.g. `"comments.edit"`) can be used as the destination parameter of
+`transitionTo` and the `{{linkTo}}` Handlebars helper, while
 `currentPath` serves as a full descriptor of each
 parent route that has been entered (e.g.
 `"admin.posts.show.comments.edit"`).
@@ -57,27 +57,27 @@ App.__container__.lookup("controller:application").get("currentPath")
 
 ## Views / Templates
 
-#### Log view lookups
+### Log view lookups
 
 ```javascript
 window.App = Ember.Application.create({
   LOG_VIEW_LOOKUPS: true
 });
 ```
 
-#### Get the View object from its DOM Element's ID
+### Get the View object from its DOM Element's ID
 
 ```javascript
 Ember.View.views['ember605']
 ```
 
-#### View all registered templates
+### View all registered templates
 
 ```javascript
 Ember.keys(Ember.TEMPLATES)
 ```
 
-#### Handlebars Debugging Helpers
+### Handlebars Debugging Helpers
 
 ```handlebars
 {{debugger}}
@@ -86,7 +86,7 @@ Ember.keys(Ember.TEMPLATES)
 
 ## Controllers
 
-#### Log generated controller 
+### Log generated controller
 
 ```javascript
 window.App = Ember.Application.create({
@@ -96,11 +96,11 @@ window.App = Ember.Application.create({
 
 ## Ember Data
 
-#### View ember-data's type maps
+### View ember-data's type maps
 
 ```javascript
 // all type maps in memory
-App.__container__.lookup('store:main').typeMaps 
+App.__container__.lookup('store:main').typeMaps
 
 // specific type map in memory
 App.__container__.lookup('store:main').typeMapFor(App.Color)
@@ -117,21 +117,21 @@ App.__container__.lookup('store:main').typeMapFor(App.Color).idToRecord["33"].ge
 
 ## Observers / Binding
 
-#### See all observers for a object, key
+### See all observers for a object, key
 
 ```javascript
 Ember.observersFor(comments, keyName);
 ```
 
-#### Log object bindings
+### Log object bindings
 
 ```javascript
 Ember.LOG_BINDINGS = true
 ```
 
 ## Miscellaneous
 
-#### Turn on resolver resolution logging
+### Turn on resolver resolution logging
 
 This option logs all the lookups that are done to the console. Custom objects
 you've created yourself have a tick, and Ember generated ones don't.
@@ -145,22 +145,22 @@ App = Ember.Application.create({
 });
 ```
 
-#### View an instance of something from the container
+### View an instance of something from the container
 
 ```javascript
 App.__container__.lookup("controller:posts")
 App.__container__.lookup("route:application")
 ```
 
-#### Dealing with deprecations
+### Dealing with deprecations
 
 ```javascript
 Ember.ENV.RAISE_ON_DEPRECATION = true
 Ember.LOG_STACKTRACE_ON_DEPRECATION = true
 ```
 
 
-#### Implement an Ember.onerror hook to log all errors in production
+### Implement an Ember.onerror hook to log all errors in production
 
 ```javascript
 Ember.onerror = function(error) {
@@ -174,7 +174,7 @@ Ember.onerror = function(error) {
 }
 ```
 
-#### Import the console
+### Import the console
 
 If you are using imports with Ember, be sure to import the console:
 
@@ -188,7 +188,7 @@ Ember = {
 };
 ```
 
-#### Errors within an `RSVP.Promise`
+### Errors within an `RSVP.Promise`
 
 There are times when dealing with promises that it seems like any errors
 are being 'swallowed', and not properly raised. This makes it extremely
@@ -206,7 +206,7 @@ Ember.RSVP.on('error', function(error) {
 });
 ```
 
-#### Errors within `Ember.run.later` ([Backburner.js](https://github.com/ebryn/backburner.js))
+### Errors within `Ember.run.later` ([Backburner.js](https://github.com/ebryn/backburner.js))
 
 Backburner has support for stitching the stacktraces together so that you can
 track down where an erroring `Ember.run.later` is being initiated from. Unfortunately,

guides/v1.11.0/understanding-ember/debugging.md

@@ -8,7 +8,7 @@ tooling for Chrome, Firefox, Safari, and Internet Explorer.
 
 ## Routing
 
-#### Log router transitions
+### Log router transitions
 
 ```javascript {data-filename=app/app.js}
 export default Ember.Application.extend({
@@ -24,7 +24,7 @@ export default Ember.Application.extend({
 ```
 ## Views / Templates
 
-#### Log view lookups
+### Log view lookups
 
 ```javascript {data-filename=config/environment.js}
 ENV.APP.LOG_VIEW_LOOKUPS = true;
@@ -34,7 +34,7 @@ ENV.APP.LOG_VIEW_LOOKUPS = true;
 Ember.keys(Ember.TEMPLATES)
 ```
 
-#### Handlebars Debugging Helpers
+### Handlebars Debugging Helpers
 
 ```handlebars
 {{debugger}}
@@ -43,29 +43,29 @@ Ember.keys(Ember.TEMPLATES)
 
 ## Controllers
 
-#### Log generated controller
+### Log generated controller
 
 ```javascript {data-filename=config/environment.js}
 ENV.APP.LOG_ACTIVE_GENERATION = true;
 ```
 
 ## Observers / Binding
 
-#### See all observers for a object, key
+### See all observers for a object, key
 
 ```javascript
 Ember.observersFor(comments, keyName);
 ```
 
-#### Log object bindings
+### Log object bindings
 
 ```javascript {data-filename=config/environments.js}
 ENV.APP.LOG_BINDINGS = true
 ```
 
 ## Miscellaneous
 
-#### Turn on resolver resolution logging
+### Turn on resolver resolution logging
 
 This option logs all the lookups that are done to the console. Custom objects
 you've created yourself have a tick, and Ember generated ones don't.
@@ -78,15 +78,15 @@ export default Ember.Application.extend({
   LOG_RESOLVER: true
 });
 ```
-#### Dealing with deprecations
+### Dealing with deprecations
 
 ```javascript
 Ember.ENV.RAISE_ON_DEPRECATION = true
 Ember.ENV.LOG_STACKTRACE_ON_DEPRECATION = true
 ```
 
 
-#### Implement an Ember.onerror hook to log all errors in production
+### Implement an Ember.onerror hook to log all errors in production
 
 ```javascript
 Ember.onerror = function(error) {
@@ -100,7 +100,7 @@ Ember.onerror = function(error) {
 }
 ```
 
-#### Import the console
+### Import the console
 
 If you are using imports with Ember, be sure to import the console:
 
@@ -114,7 +114,7 @@ Ember = {
 };
 ```
 
-#### Errors within an `RSVP.Promise`
+### Errors within an `RSVP.Promise`
 
 There are times when dealing with promises that it seems like any errors
 are being 'swallowed', and not properly raised. This makes it extremely
@@ -132,7 +132,7 @@ Ember.RSVP.on('error', function(error) {
 });
 ```
 
-#### Errors within `Ember.run.later` ([Backburner.js](https://github.com/ebryn/backburner.js))
+### Errors within `Ember.run.later` ([Backburner.js](https://github.com/ebryn/backburner.js))
 
 Backburner has support for stitching the stacktraces together so that you can
 track down where an erroring `Ember.run.later` is being initiated from. Unfortunately,