ember-source 4.5.0-alpha.5 → 4.6.0-alpha.2

package/docs/data.json

@@ -3,7 +3,7 @@
     "name": "The Ember API",
     "description": "The Ember API: a framework for building ambitious web applications",
     "url": "https://emberjs.com/",
-    "version": "4.5.0-alpha.5"
+    "version": "4.6.0-alpha.2"
   },
   "files": {
     "node_modules/rsvp/lib/rsvp/promise/all.js": {
@@ -1334,15 +1334,8 @@
       },
       "namespaces": {}
     },
-    "packages/@ember/controller/lib/controller_mixin.d.ts": {
-      "name": "packages/@ember/controller/lib/controller_mixin.d.ts",
-      "modules": {},
-      "classes": {},
-      "fors": {},
-      "namespaces": {}
-    },
-    "packages/@ember/controller/lib/controller_mixin.js": {
-      "name": "packages/@ember/controller/lib/controller_mixin.js",
+    "packages/@ember/controller/lib/controller_mixin.ts": {
+      "name": "packages/@ember/controller/lib/controller_mixin.ts",
       "modules": {},
       "classes": {
         "Ember.ControllerMixin": 1
@@ -1480,8 +1473,8 @@
       },
       "namespaces": {}
     },
-    "packages/@ember/object/lib/computed/computed_macros.js": {
-      "name": "packages/@ember/object/lib/computed/computed_macros.js",
+    "packages/@ember/object/lib/computed/computed_macros.ts": {
+      "name": "packages/@ember/object/lib/computed/computed_macros.ts",
       "modules": {
         "@ember/object": 1
       },
@@ -1491,8 +1484,8 @@
       },
       "namespaces": {}
     },
-    "packages/@ember/object/lib/computed/reduce_computed_macros.js": {
-      "name": "packages/@ember/object/lib/computed/reduce_computed_macros.js",
+    "packages/@ember/object/lib/computed/reduce_computed_macros.ts": {
+      "name": "packages/@ember/object/lib/computed/reduce_computed_macros.ts",
       "modules": {},
       "classes": {},
       "fors": {
@@ -1764,7 +1757,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 158,
+      "line": 156,
       "access": "public",
       "tagname": ""
     },
@@ -1787,7 +1780,7 @@
       "namespaces": {},
       "tag": "main",
       "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
-      "line": 45,
+      "line": 47,
       "description": "[Glimmer](https://github.com/tildeio/glimmer) is a templating engine used by Ember.js that is compatible with a subset of the [Handlebars](http://handlebarsjs.com/) syntax.\n\n### Showing a property\n\nTemplates manage the flow of an application's UI, and display state (through\nthe DOM) to a user. For example, given a component with the property \"name\",\nthat component's template can use the name in several ways:\n\n```app/components/person-profile.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  name: 'Jill'\n});\n```\n\n```app/components/person-profile.hbs\n{{this.name}}\n<div>{{this.name}}</div>\n<span data-name={{this.name}}></span>\n```\n\nAny time the \"name\" property on the component changes, the DOM will be\nupdated.\n\nProperties can be chained as well:\n\n```handlebars\n{{@aUserModel.name}}\n<div>{{@listOfUsers.firstObject.name}}</div>\n```\n\n### Using Ember helpers\n\nWhen content is passed in mustaches `{{}}`, Ember will first try to find a helper\nor component with that name. For example, the `if` helper:\n\n```app/components/person-profile.hbs\n{{if this.name \"I have a name\" \"I have no name\"}}\n<span data-has-name={{if this.name true}}></span>\n```\n\nThe returned value is placed where the `{{}}` is called. The above style is\ncalled \"inline\". A second style of helper usage is called \"block\". For example:\n\n```handlebars\n{{#if this.name}}\n  I have a name\n{{else}}\n  I have no name\n{{/if}}\n```\n\nThe block form of helpers allows you to control how the UI is created based\non the values of properties.\nA third form of helper is called \"nested\". For example here the concat\nhelper will add \" Doe\" to a displayed name if the person has no last name:\n\n```handlebars\n<span data-name={{concat this.firstName (\n  if this.lastName (concat \" \" this.lastName) \"Doe\"\n)}}></span>\n```\n\nEmber's built-in helpers are described under the [Ember.Templates.helpers](/ember/release/classes/Ember.Templates.helpers)\nnamespace. Documentation on creating custom helpers can be found under\n[helper](/ember/release/functions/@ember%2Fcomponent%2Fhelper/helper) (or\nunder [Helper](/ember/release/classes/Helper) if a helper requires access to\ndependency injection).\n\n### Invoking a Component\n\nEmber components represent state to the UI of an application. Further\nreading on components can be found under [Component](/ember/release/classes/Component).",
       "itemtype": "main"
     },
@@ -1909,7 +1902,7 @@
       "tag": "module",
       "file": "packages/@ember/-internals/glimmer/lib/glimmer-tracking-docs.ts",
       "line": 1,
-      "description": "In order to tell Ember a value might change, we need to mark it as trackable.\nTrackable values are values that:\n\n- Can change over their component’s lifetime and\n- Should cause Ember to rerender if and when they change\n\nWe can do this by marking the field with the `@tracked` decorator.",
+      "description": "In order to tell Ember a value might change, we need to mark it as trackable.\nTrackable values are values that:\n\n- Can change over their component’s lifetime and\n- Should cause Ember to rerender if and when they change\n\nWe can do this by marking the field with the `@tracked` decorator.\n\n### Caching a getter value\n\nThe `@cached` decorator can be used on getters in order to cache the\nreturn value of the getter.\n\nThis method adds an extra overhead to each memoized getter, therefore caching\nthe values should not be the default strategy, but used in last resort.",
       "access": "public",
       "tagname": ""
     },
@@ -2008,7 +2001,7 @@
       },
       "tag": "module",
       "file": "packages/@ember/application/instance.ts",
-      "line": 325
+      "line": 326
     },
     "@ember/array": {
       "name": "@ember/array",
@@ -2026,7 +2019,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/-internals/runtime/lib/system/array_proxy.ts",
-      "line": 58
+      "line": 52
     },
     "@ember/enumerable": {
       "name": "@ember/enumerable",
@@ -2218,7 +2211,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/runloop/index.ts",
-      "line": 97
+      "line": 98
     },
     "@ember/service": {
       "name": "@ember/service",
@@ -2234,7 +2227,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/service/index.ts",
-      "line": 90,
+      "line": 87,
       "access": "public",
       "tagname": ""
     },
@@ -2268,7 +2261,7 @@
       },
       "tag": "module",
       "file": "packages/ember-testing/lib/adapters/adapter.js",
-      "line": 11
+      "line": 7
     }
   },
   "classes": {
@@ -2338,7 +2331,7 @@
       "module": "rsvp",
       "namespace": "",
       "file": "packages/@ember/-internals/container/lib/container.ts",
-      "line": 51,
+      "line": 53,
       "description": "A container used to instantiate and cache objects.\n\nEvery `Container` must be associated with a `Registry`, which is referenced\nto determine the factory and options that should be used to instantiate\nobjects.\n\nThe public API for `Container` is still in flux and should not be considered\nstable.",
       "access": "private",
       "tagname": ""
@@ -2354,7 +2347,7 @@
       "module": "rsvp",
       "namespace": "",
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 56,
+      "line": 57,
       "description": "A registry used to store factory and option information keyed\nby type.\n\nA `Registry` stores the factory and option information needed by a\n`Container` to instantiate and cache objects.\n\nThe API for `Registry` is still in flux and should not be considered stable.",
       "access": "private",
       "tagname": "",
@@ -2388,7 +2381,7 @@
       "module": "@ember/debug",
       "namespace": "",
       "file": "packages/@ember/-internals/extension-support/lib/container_debug_adapter.ts",
-      "line": 16,
+      "line": 12,
       "description": "The `ContainerDebugAdapter` helps the container and resolver interface\nwith tools that debug Ember such as the\n[Ember Inspector](https://github.com/emberjs/ember-inspector)\nfor Chrome and Firefox.\n\nThis class can be extended by a custom resolver implementer\nto override some of the methods with library-specific code.\n\nThe methods likely to be overridden are:\n\n* `canCatalogEntriesByType`\n* `catalogEntriesByType`\n\nThe adapter will need to be registered\nin the application's container as `container-debug-adapter:main`.\n\nExample:\n\n```javascript\nApplication.initializer({\n  name: \"containerDebugAdapter\",\n\n  initialize(application) {\n    application.register('container-debug-adapter:main', require('app/container-debug-adapter'));\n  }\n});\n```",
       "extends": "EmberObject",
       "since": "1.5.0",
@@ -2406,7 +2399,7 @@
       "module": "@ember/debug",
       "namespace": "",
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 158,
+      "line": 156,
       "description": "The `DataAdapter` helps a data persistence library\ninterface with tools that debug Ember such\nas the [Ember Inspector](https://github.com/emberjs/ember-inspector)\nfor Chrome and Firefox.\n\nThis class will be extended by a persistence library\nwhich will override some of the methods with\nlibrary-specific code.\n\nThe methods likely to be overridden are:\n\n* `getFilters`\n* `detect`\n* `columnsForType`\n* `getRecords`\n* `getRecordColumnValues`\n* `getRecordKeywords`\n* `getRecordFilterValues`\n* `getRecordColor`\n\nThe adapter will need to be registered\nin the application's container as `dataAdapter:main`.\n\nExample:\n\n```javascript\nApplication.initializer({\n  name: \"data-adapter\",\n\n  initialize: function(application) {\n    application.register('data-adapter:main', DS.DataAdapter);\n  }\n});\n```",
       "extends": "EmberObject",
       "access": "public",
@@ -2471,7 +2464,7 @@
       "module": "ember",
       "namespace": "",
       "file": "packages/@ember/-internals/glimmer/lib/utils/curly-component-state-bucket.ts",
-      "line": 15,
+      "line": 17,
       "description": "Represents the internal state of the component.",
       "access": "private",
       "tagname": ""
@@ -2498,7 +2491,7 @@
       "module": "@ember/component",
       "namespace": "",
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 38,
+      "line": 39,
       "description": "A component is a reusable UI element that consists of a `.hbs` template and an\noptional JavaScript class that defines its behavior. For example, someone\nmight make a `button` in the template and handle the click behavior in the\nJavaScript file that shares the same name as the template.\n\nComponents are broken down into two categories:\n\n- Components _without_ JavaScript, that are based only on a template. These\n  are called Template-only or TO components.\n- Components _with_ JavaScript, which consist of a template and a backing\n  class.\n\nEmber ships with two types of JavaScript classes for components:\n\n1. Glimmer components, imported from `@glimmer/component`, which are the\n   default component's for Ember Octane (3.15) and more recent editions.\n2. Classic components, imported from `@ember/component`, which were the\n   default for older editions of Ember (pre 3.15).\n\nBelow is the documentation for Classic components. If you are looking for the\nAPI documentation for Template-only or Glimmer components, it is\n[available here](/ember/release/modules/@glimmer%2Fcomponent).\n\n## Defining a Classic Component\n\nIf you want to customize the component in order to handle events, transform\narguments or maintain internal state, you implement a subclass of `Component`.\n\nOne example is to add computed properties to your component:\n\n```app/components/person-profile.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  displayName: computed('person.title', 'person.firstName', 'person.lastName', function() {\n    let { title, firstName, lastName } = this.person;\n\n    if (title) {\n      return `${title} ${lastName}`;\n    } else {\n      return `${firstName} ${lastName}`;\n    }\n  })\n});\n```\n\nAnd then use it in the component's template:\n\n```app/templates/components/person-profile.hbs\n<h1>{{this.displayName}}</h1>\n{{yield}}\n```\n\n## Customizing a Classic Component's HTML Element in JavaScript\n\n### HTML Tag\n\nThe default HTML tag name used for a component's HTML representation is `div`.\nThis can be customized by setting the `tagName` property.\n\nConsider the following component class:\n\n```app/components/emphasized-paragraph.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  tagName: 'em'\n});\n```\n\nWhen invoked, this component would produce output that looks something like\nthis:\n\n```html\n<em id=\"ember1\" class=\"ember-view\"></em>\n```\n\n### HTML `class` Attribute\n\nThe HTML `class` attribute of a component's tag can be set by providing a\n`classNames` property that is set to an array of strings:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  classNames: ['my-class', 'my-other-class']\n});\n```\n\nInvoking this component will produce output that looks like this:\n\n```html\n<div id=\"ember1\" class=\"ember-view my-class my-other-class\"></div>\n```\n\n`class` attribute values can also be set by providing a `classNameBindings`\nproperty set to an array of properties names for the component. The return\nvalue of these properties will be added as part of the value for the\ncomponents's `class` attribute. These properties can be computed properties:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\nimport { computed } from '@ember/object';\n\nexport default Component.extend({\n  classNames: ['my-class', 'my-other-class'],\n  classNameBindings: ['propertyA', 'propertyB'],\n\n  propertyA: 'from-a',\n  propertyB: computed(function() {\n    if (someLogic) { return 'from-b'; }\n  })\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view my-class my-other-class from-a from-b\"></div>\n```\n\nNote that `classNames` and `classNameBindings` is in addition to the `class`\nattribute passed with the angle bracket invocation syntax. Therefore, if this\ncomponent was invoked like so:\n\n```handlebars\n<MyWidget class=\"from-invocation\" />\n```\n\nThe resulting HTML will look similar to this:\n\n```html\n<div id=\"ember1\" class=\"from-invocation ember-view my-class my-other-class from-a from-b\"></div>\n```\n\nIf the value of a class name binding returns a boolean the property name\nitself will be used as the class name if the property is true. The class name\nwill not be added if the value is `false` or `undefined`.\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  classNameBindings: ['hovered'],\n\n  hovered: true\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view hovered\"></div>\n```\n\n### Custom Class Names for Boolean Values\n\nWhen using boolean class name bindings you can supply a string value other\nthan the property name for use as the `class` HTML attribute by appending the\npreferred value after a \":\" character when defining the binding:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  classNameBindings: ['awesome:so-very-cool'],\n\n  awesome: true\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view so-very-cool\"></div>\n```\n\nBoolean value class name bindings whose property names are in a\ncamelCase-style format will be converted to a dasherized format:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  classNameBindings: ['isUrgent'],\n\n  isUrgent: true\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view is-urgent\"></div>\n```\n\nClass name bindings can also refer to object values that are found by\ntraversing a path relative to the component itself:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\nimport EmberObject from '@ember/object';\n\nexport default Component.extend({\n  classNameBindings: ['messages.empty'],\n\n  messages: EmberObject.create({\n    empty: true\n  })\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view empty\"></div>\n```\n\nIf you want to add a class name for a property which evaluates to true and\nand a different class name if it evaluates to false, you can pass a binding\nlike this:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  classNameBindings: ['isEnabled:enabled:disabled'],\n  isEnabled: true\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view enabled\"></div>\n```\n\nWhen isEnabled is `false`, the resulting HTML representation looks like this:\n\n```html\n<div id=\"ember1\" class=\"ember-view disabled\"></div>\n```\n\nThis syntax offers the convenience to add a class if a property is `false`:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\n// Applies no class when isEnabled is true and class 'disabled' when isEnabled is false\nexport default Component.extend({\n  classNameBindings: ['isEnabled::disabled'],\n  isEnabled: true\n});\n```\n\nInvoking this component when the `isEnabled` property is true will produce\nHTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view\"></div>\n```\n\nInvoking it when the `isEnabled` property on the component is `false` will\nproduce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view disabled\"></div>\n```\n\nUpdates to the value of a class name binding will result in automatic update\nof the  HTML `class` attribute in the component's rendered HTML\nrepresentation. If the value becomes `false` or `undefined` the class name\nwill be removed.\n\nBoth `classNames` and `classNameBindings` are concatenated properties. See\n[EmberObject](/ember/release/classes/EmberObject) documentation for more\ninformation about concatenated properties.\n\n### Other HTML Attributes\n\nThe HTML attribute section of a component's tag can be set by providing an\n`attributeBindings` property set to an array of property names on the component.\nThe return value of these properties will be used as the value of the component's\nHTML associated attribute:\n\n```app/components/my-anchor.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  tagName: 'a',\n  attributeBindings: ['href'],\n\n  href: 'http://google.com'\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<a id=\"ember1\" class=\"ember-view\" href=\"http://google.com\"></a>\n```\n\nOne property can be mapped on to another by placing a \":\" between\nthe source property and the destination property:\n\n```app/components/my-anchor.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  tagName: 'a',\n  attributeBindings: ['url:href'],\n\n  url: 'http://google.com'\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<a id=\"ember1\" class=\"ember-view\" href=\"http://google.com\"></a>\n```\n\nHTML attributes passed with angle bracket invocations will take precedence\nover those specified in `attributeBindings`. Therefore, if this component was\ninvoked like so:\n\n```handlebars\n<MyAnchor href=\"http://bing.com\" @url=\"http://google.com\" />\n```\n\nThe resulting HTML will looks like this:\n\n```html\n<a id=\"ember1\" class=\"ember-view\" href=\"http://bing.com\"></a>\n```\n\nNote that the `href` attribute is ultimately set to `http://bing.com`,\ndespite it having attribute binidng to the `url` property, which was\nset to `http://google.com`.\n\nNamespaced attributes (e.g. `xlink:href`) are supported, but have to be\nmapped, since `:` is not a valid character for properties in Javascript:\n\n```app/components/my-use.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  tagName: 'use',\n  attributeBindings: ['xlinkHref:xlink:href'],\n\n  xlinkHref: '#triangle'\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<use xlink:href=\"#triangle\"></use>\n```\n\nIf the value of a property monitored by `attributeBindings` is a boolean, the\nattribute will be present or absent depending on the value:\n\n```app/components/my-text-input.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  tagName: 'input',\n  attributeBindings: ['disabled'],\n\n  disabled: false\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<input id=\"ember1\" class=\"ember-view\" />\n```\n\n`attributeBindings` can refer to computed properties:\n\n```app/components/my-text-input.js\nimport Component from '@ember/component';\nimport { computed } from '@ember/object';\n\nexport default Component.extend({\n  tagName: 'input',\n  attributeBindings: ['disabled'],\n\n  disabled: computed(function() {\n    if (someLogic) {\n      return true;\n    } else {\n      return false;\n    }\n  })\n});\n```\n\nTo prevent setting an attribute altogether, use `null` or `undefined` as the\nvalue of the property used in `attributeBindings`:\n\n```app/components/my-text-input.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  tagName: 'form',\n  attributeBindings: ['novalidate'],\n  novalidate: null\n});\n```\n\nUpdates to the property of an attribute binding will result in automatic\nupdate of the  HTML attribute in the component's HTML output.\n\n`attributeBindings` is a concatenated property. See\n[EmberObject](/ember/release/classes/EmberObject) documentation for more\ninformation about concatenated properties.\n\n## Layouts\n\nThe `layout` property can be used to dynamically specify a template associated\nwith a component class, instead of relying on Ember to link together a\ncomponent class and a template based on file names.\n\nIn general, applications should not use this feature, but it's commonly used\nin addons for historical reasons.\n\nThe `layout` property should be set to the default export of a template\nmodule, which is the name of a template file without the `.hbs` extension.\n\n```app/templates/components/person-profile.hbs\n<h1>Person's Title</h1>\n<div class='details'>{{yield}}</div>\n```\n\n```app/components/person-profile.js\n  import Component from '@ember/component';\n  import layout from '../templates/components/person-profile';\n\n  export default Component.extend({\n    layout\n  });\n```\n\nIf you invoke the component:\n\n```handlebars\n<PersonProfile>\n  <h2>Chief Basket Weaver</h2>\n  <h3>Fisherman Industries</h3>\n</PersonProfile>\n```\n\nor\n\n```handlebars\n{{#person-profile}}\n  <h2>Chief Basket Weaver</h2>\n  <h3>Fisherman Industries</h3>\n{{/person-profile}}\n```\n\nIt will result in the following HTML output:\n\n```html\n<h1>Person's Title</h1>\n  <div class=\"details\">\n  <h2>Chief Basket Weaver</h2>\n  <h3>Fisherman Industries</h3>\n</div>\n```\n\n## Handling Browser Events\n\nComponents can respond to user-initiated events in one of three ways: passing\nactions with angle bracket invocation, adding event handler methods to the\ncomponent's class, or adding actions to the component's template.\n\n### Passing Actions With Angle Bracket Invocation\n\nFor one-off events specific to particular instance of a component, it is possible\nto pass actions to the component's element using angle bracket invocation syntax.\n\n```handlebars\n<MyWidget {{action 'firstWidgetClicked'}} />\n\n<MyWidget {{action 'secondWidgetClicked'}} />\n```\n\nIn this case, when the first component is clicked on, Ember will invoke the\n`firstWidgetClicked` action. When the second component is clicked on, Ember\nwill invoke the `secondWidgetClicked` action instead.\n\nBesides `{{action}}`, it is also possible to pass any arbitrary element modifiers\nusing the angle bracket invocation syntax.\n\n### Event Handler Methods\n\nComponents can also respond to user-initiated events by implementing a method\nthat matches the event name. This approach is appropriate when the same event\nshould be handled by all instances of the same component.\n\nAn event object will be passed as the argument to the event handler method.\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  click(event) {\n    // `event.target` is either the component's element or one of its children\n    let tag = event.target.tagName.toLowerCase();\n    console.log('clicked on a `<${tag}>` HTML element!');\n  }\n});\n```\n\nIn this example, whenever the user clicked anywhere inside the component, it\nwill log a message to the console.\n\nIt is possible to handle event types other than `click` by implementing the\nfollowing event handler methods. In addition, custom events can be registered\nby using `Application.customEvents`.\n\nTouch events:\n\n* `touchStart`\n* `touchMove`\n* `touchEnd`\n* `touchCancel`\n\nKeyboard events:\n\n* `keyDown`\n* `keyUp`\n* `keyPress`\n\nMouse events:\n\n* `mouseDown`\n* `mouseUp`\n* `contextMenu`\n* `click`\n* `doubleClick`\n* `focusIn`\n* `focusOut`\n\nForm events:\n\n* `submit`\n* `change`\n* `focusIn`\n* `focusOut`\n* `input`\n\nDrag and drop events:\n\n* `dragStart`\n* `drag`\n* `dragEnter`\n* `dragLeave`\n* `dragOver`\n* `dragEnd`\n* `drop`\n\n### `{{action}}` Helper\n\nInstead of handling all events of a particular type anywhere inside the\ncomponent's element, you may instead want to limit it to a particular\nelement in the component's template. In this case, it would be more\nconvenient to implement an action instead.\n\nFor example, you could implement the action `hello` for the `person-profile`\ncomponent:\n\n```app/components/person-profile.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  actions: {\n    hello(name) {\n      console.log(\"Hello\", name);\n    }\n  }\n});\n```\n\nAnd then use it in the component's template:\n\n```app/templates/components/person-profile.hbs\n<h1>{{@person.name}}</h1>\n\n<button {{action 'hello' @person.name}}>\n  Say Hello to {{@person.name}}\n</button>\n```\n\nWhen the user clicks the button, Ember will invoke the `hello` action,\npassing in the current value of `@person.name` as an argument.\n\nSee [Ember.Templates.helpers.action](/ember/release/classes/Ember.Templates.helpers/methods/action?anchor=action).",
       "extends": "Ember.CoreView",
       "uses": [
@@ -2533,7 +2526,7 @@
       "module": "@ember/component",
       "namespace": "",
       "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
-      "line": 45,
+      "line": 47,
       "description": "Ember Helpers are functions that can compute values, and are used in templates.\nFor example, this code calls a helper named `format-currency`:\n\n```app/templates/application.hbs\n<Cost @cents={{230}} />\n```\n\n```app/components/cost.hbs\n<div>{{format-currency @cents currency=\"$\"}}</div>\n```\n\nAdditionally a helper can be called as a nested helper.\nIn this example, we show the formatted currency value if the `showMoney`\nnamed argument is truthy.\n\n```handlebars\n{{if @showMoney (format-currency @cents currency=\"$\")}}\n```\n\nHelpers defined using a class must provide a `compute` function. For example:\n\n```app/helpers/format-currency.js\nimport Helper from '@ember/component/helper';\n\nexport default class extends Helper {\n  compute([cents], { currency }) {\n    return `${currency}${cents * 0.01}`;\n  }\n}\n```\n\nEach time the input to a helper changes, the `compute` function will be\ncalled again.\n\nAs instances, these helpers also have access to the container and will accept\ninjected dependencies.\n\nAdditionally, class helpers can call `recompute` to force a new computation.",
       "extends": "CoreObject",
       "access": "public",
@@ -2584,7 +2577,7 @@
       "module": "@ember/object",
       "namespace": "",
       "file": "packages/@ember/-internals/metal/lib/computed.ts",
-      "line": 74,
+      "line": 77,
       "description": "`@computed` is a decorator that turns a JavaScript getter and setter into a\ncomputed property, which is a _cached, trackable value_. By default the getter\nwill only be called once and the result will be cached. You can specify\nvarious properties that your computed property depends on. This will force the\ncached result to be cleared if the dependencies are modified, and lazily recomputed the next time something asks for it.\n\nIn the following example we decorate a getter - `fullName` -  by calling\n`computed` with the property dependencies (`firstName` and `lastName`) as\narguments. The `fullName` getter will be called once (regardless of how many\ntimes it is accessed) as long as its dependencies do not change. Once\n`firstName` or `lastName` are updated any future calls to `fullName` will\nincorporate the new values, and any watchers of the value such as templates\nwill be updated:\n\n```javascript\nimport { computed, set } from '@ember/object';\n\nclass Person {\n  constructor(firstName, lastName) {\n    set(this, 'firstName', firstName);\n    set(this, 'lastName', lastName);\n  }\n\n  @computed('firstName', 'lastName')\n  get fullName() {\n    return `${this.firstName} ${this.lastName}`;\n  }\n});\n\nlet tom = new Person('Tom', 'Dale');\n\ntom.fullName; // 'Tom Dale'\n```\n\nYou can also provide a setter, which will be used when updating the computed\nproperty. Ember's `set` function must be used to update the property\nsince it will also notify observers of the property:\n\n```javascript\nimport { computed, set } from '@ember/object';\n\nclass Person {\n  constructor(firstName, lastName) {\n    set(this, 'firstName', firstName);\n    set(this, 'lastName', lastName);\n  }\n\n  @computed('firstName', 'lastName')\n  get fullName() {\n    return `${this.firstName} ${this.lastName}`;\n  }\n\n  set fullName(value) {\n    let [firstName, lastName] = value.split(' ');\n\n    set(this, 'firstName', firstName);\n    set(this, 'lastName', lastName);\n  }\n});\n\nlet person = new Person();\n\nset(person, 'fullName', 'Peter Wagenet');\nperson.firstName; // 'Peter'\nperson.lastName;  // 'Wagenet'\n```\n\nYou can also pass a getter function or object with `get` and `set` functions\nas the last argument to the computed decorator. This allows you to define\ncomputed property _macros_:\n\n```js\nimport { computed } from '@ember/object';\n\nfunction join(...keys) {\n  return computed(...keys, function() {\n    return keys.map(key => this[key]).join(' ');\n  });\n}\n\nclass Person {\n  @join('firstName', 'lastName')\n  fullName;\n}\n```\n\nNote that when defined this way, getters and setters receive the _key_ of the\nproperty they are decorating as the first argument. Setters receive the value\nthey are setting to as the second argument instead. Additionally, setters must\n_return_ the value that should be cached:\n\n```javascript\nimport { computed, set } from '@ember/object';\n\nfunction fullNameMacro(firstNameKey, lastNameKey) {\n  return computed(firstNameKey, lastNameKey, {\n    get() {\n      return `${this[firstNameKey]} ${this[lastNameKey]}`;\n    }\n\n    set(key, value) {\n      let [firstName, lastName] = value.split(' ');\n\n      set(this, firstNameKey, firstName);\n      set(this, lastNameKey, lastName);\n\n      return value;\n    }\n  });\n}\n\nclass Person {\n  constructor(firstName, lastName) {\n    set(this, 'firstName', firstName);\n    set(this, 'lastName', lastName);\n  }\n\n  @fullNameMacro('firstName', 'lastName') fullName;\n});\n\nlet person = new Person();\n\nset(person, 'fullName', 'Peter Wagenet');\nperson.firstName; // 'Peter'\nperson.lastName;  // 'Wagenet'\n```\n\nComputed properties can also be used in classic classes. To do this, we\nprovide the getter and setter as the last argument like we would for a macro,\nand we assign it to a property on the class definition. This is an _anonymous_\ncomputed macro:\n\n```javascript\nimport EmberObject, { computed, set } from '@ember/object';\n\nlet Person = EmberObject.extend({\n  // these will be supplied by `create`\n  firstName: null,\n  lastName: null,\n\n  fullName: computed('firstName', 'lastName', {\n    get() {\n      return `${this.firstName} ${this.lastName}`;\n    }\n\n    set(key, value) {\n      let [firstName, lastName] = value.split(' ');\n\n      set(this, 'firstName', firstName);\n      set(this, 'lastName', lastName);\n\n      return value;\n    }\n  })\n});\n\nlet tom = Person.create({\n  firstName: 'Tom',\n  lastName: 'Dale'\n});\n\ntom.get('fullName') // 'Tom Dale'\n```\n\nYou can overwrite computed property without setters with a normal property (no\nlonger computed) that won't change if dependencies change. You can also mark\ncomputed property as `.readOnly()` and block all attempts to set it.\n\n```javascript\nimport { computed, set } from '@ember/object';\n\nclass Person {\n  constructor(firstName, lastName) {\n    set(this, 'firstName', firstName);\n    set(this, 'lastName', lastName);\n  }\n\n  @computed('firstName', 'lastName').readOnly()\n  get fullName() {\n    return `${this.firstName} ${this.lastName}`;\n  }\n});\n\nlet person = new Person();\nperson.set('fullName', 'Peter Wagenet'); // Uncaught Error: Cannot set read-only property \"fullName\" on object: <(...):emberXXX>\n```\n\nAdditional resources:\n- [Decorators RFC](https://github.com/emberjs/rfcs/blob/master/text/0408-decorators.md)\n- [New CP syntax RFC](https://github.com/emberjs/rfcs/blob/master/text/0011-improved-cp-syntax.md)\n- [New computed syntax explained in \"Ember 1.12 released\" ](https://emberjs.com/blog/2015/05/13/ember-1-12-released.html#toc_new-computed-syntax)",
       "access": "public",
       "tagname": ""
@@ -2622,7 +2615,7 @@
       "module": "@ember/object",
       "namespace": "",
       "file": "packages/@ember/-internals/metal/lib/decorator.ts",
-      "line": 49,
+      "line": 50,
       "description": "Objects of this type can implement an interface to respond to requests to\nget and set. The default implementation handles simple properties.",
       "access": "private",
       "tagname": ""
@@ -2671,7 +2664,7 @@
       "module": "ember",
       "namespace": "Ember",
       "file": "packages/@ember/-internals/metal/lib/injected_property.ts",
-      "line": 19,
+      "line": 20,
       "description": "Read-only property that returns the result of a container lookup.",
       "is_constructor": 1,
       "params": [
@@ -2728,7 +2721,7 @@
       "module": "@ember/object",
       "namespace": "",
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 445,
+      "line": 442,
       "description": "The `Mixin` class allows you to create mixins, whose properties can be\nadded to other classes. For instance,\n\n```javascript\nimport Mixin from '@ember/object/mixin';\n\nconst EditableMixin = Mixin.create({\n  edit() {\n    console.log('starting to edit');\n    this.set('isEditing', true);\n  },\n  isEditing: false\n});\n```\n\n```javascript\nimport EmberObject from '@ember/object';\nimport EditableMixin from '../mixins/editable';\n\n// Mix mixins into classes by passing them as the first arguments to\n// `.extend.`\nconst Comment = EmberObject.extend(EditableMixin, {\n  post: null\n});\n\nlet comment = Comment.create({\n  post: somePost\n});\n\ncomment.edit(); // outputs 'starting to edit'\n```\n\nNote that Mixins are created with `Mixin.create`, not\n`Mixin.extend`.\n\nNote that mixins extend a constructor's prototype so arrays and object literals\ndefined as properties will be shared amongst objects that implement the mixin.\nIf you want to define a property in a mixin that is not shared, you can define\nit either as a computed property or have it be created on initialization of the object.\n\n```javascript\n// filters array will be shared amongst any object implementing mixin\nimport Mixin from '@ember/object/mixin';\nimport { A } from '@ember/array';\n\nconst FilterableMixin = Mixin.create({\n  filters: A()\n});\n```\n\n```javascript\nimport Mixin from '@ember/object/mixin';\nimport { A } from '@ember/array';\nimport { computed } from '@ember/object';\n\n// filters will be a separate array for every object implementing the mixin\nconst FilterableMixin = Mixin.create({\n  filters: computed(function() {\n    return A();\n  })\n});\n```\n\n```javascript\nimport Mixin from '@ember/object/mixin';\nimport { A } from '@ember/array';\n\n// filters will be created as a separate array during the object's initialization\nconst Filterable = Mixin.create({\n  filters: null,\n\n  init() {\n    this._super(...arguments);\n    this.set(\"filters\", A());\n  }\n});\n```",
       "access": "public",
       "tagname": ""
@@ -2778,8 +2771,8 @@
       ],
       "module": "ember",
       "namespace": "Ember",
-      "file": "packages/@ember/controller/lib/controller_mixin.js",
-      "line": 11,
+      "file": "packages/@ember/controller/lib/controller_mixin.ts",
+      "line": 17,
       "uses": [
         "Ember.ActionHandler"
       ],
@@ -2881,7 +2874,7 @@
       "module": "@ember/routing",
       "namespace": "",
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 23,
+      "line": 24,
       "description": "The Router service is the public API that provides access to the router.\n\nThe immediate benefit of the Router service is that you can inject it into components,\ngiving them a friendly way to initiate transitions and ask questions about the current\nglobal router state.\n\nIn this example, the Router service is injected into a component to initiate a transition\nto a dedicated route:\n\n```app/components/example.js\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\nimport { service } from '@ember/service';\n\nexport default class ExampleComponent extends Component {\n  @service router;\n\n  @action\n  next() {\n    this.router.transitionTo('other.route');\n  }\n}\n```\n\nLike any service, it can also be injected into helpers, routes, etc.",
       "access": "public",
       "tagname": "",
@@ -2962,7 +2955,7 @@
       "module": "@ember/routing",
       "namespace": "",
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 85,
+      "line": 84,
       "description": "The `Route` class is used to define individual routes. Refer to\nthe [routing guide](https://guides.emberjs.com/release/routing/) for documentation.",
       "extends": "EmberObject",
       "uses": [
@@ -2984,7 +2977,7 @@
       "module": "@ember/routing",
       "namespace": "",
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 141,
+      "line": 137,
       "description": "The `EmberRouter` class manages the application state and URLs. Refer to\nthe [routing guide](https://guides.emberjs.com/release/routing/) for documentation.",
       "extends": "EmberObject",
       "uses": [
@@ -3022,7 +3015,7 @@
       "module": "ember",
       "namespace": "Ember",
       "file": "packages/@ember/-internals/runtime/lib/mixins/-proxy.ts",
-      "line": 62,
+      "line": 63,
       "description": "`Ember.ProxyMixin` forwards all properties not defined by the proxy itself\nto a proxied `content` object.  See ObjectProxy for more details.",
       "access": "private",
       "tagname": ""
@@ -3152,7 +3145,7 @@
       "module": "ember",
       "namespace": "",
       "file": "packages/@ember/-internals/runtime/lib/mixins/container_proxy.ts",
-      "line": 18,
+      "line": 19,
       "description": "ContainerProxyMixin is used to provide public access to specific\ncontainer functionality.",
       "access": "private",
       "tagname": ""
@@ -3299,7 +3292,7 @@
       "module": "@ember/array",
       "namespace": "",
       "file": "packages/@ember/-internals/runtime/lib/system/array_proxy.ts",
-      "line": 58,
+      "line": 52,
       "description": "An ArrayProxy wraps any other object that implements `Array` and/or\n`MutableArray,` forwarding all requests. This makes it very useful for\na number of binding use cases or other cases where being able to swap\nout the underlying array is useful.\n\nA simple example of usage:\n\n```javascript\nimport { A } from '@ember/array';\nimport ArrayProxy from '@ember/array/proxy';\n\nlet pets = ['dog', 'cat', 'fish'];\nlet ap = ArrayProxy.create({ content: A(pets) });\n\nap.get('firstObject');                        // 'dog'\nap.set('content', ['amoeba', 'paramecium']);\nap.get('firstObject');                        // 'amoeba'\n```\n\nThis class can also be useful as a layer to transform the contents of\nan array, as they are accessed. This can be done by overriding\n`objectAtContent`:\n\n```javascript\nimport { A } from '@ember/array';\nimport ArrayProxy from '@ember/array/proxy';\n\nlet pets = ['dog', 'cat', 'fish'];\nlet ap = ArrayProxy.create({\n    content: A(pets),\n    objectAtContent: function(idx) {\n        return this.get('content').objectAt(idx).toUpperCase();\n    }\n});\n\nap.get('firstObject'); // . 'DOG'\n```\n\nWhen overriding this class, it is important to place the call to\n`_super` *after* setting `content` so the internal observers have\na chance to fire properly:\n\n```javascript\nimport { A } from '@ember/array';\nimport ArrayProxy from '@ember/array/proxy';\n\nexport default ArrayProxy.extend({\n  init() {\n    this.set('content', A(['dog', 'cat', 'fish']));\n    this._super(...arguments);\n  }\n});\n```",
       "extends": "EmberObject",
       "uses": [
@@ -3319,7 +3312,7 @@
       "module": "@ember/object",
       "namespace": "",
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.ts",
-      "line": 174,
+      "line": 173,
       "description": "`CoreObject` is the base class for all Ember constructs. It establishes a\nclass system based on Ember's Mixin system, and provides the basis for the\nEmber Object Model. `CoreObject` should generally not be used directly,\ninstead you should use `EmberObject`.\n\n## Usage\n\nYou can define a class by extending from `CoreObject` using the `extend`\nmethod:\n\n```js\nconst Person = CoreObject.extend({\n  name: 'Tomster',\n});\n```\n\nFor detailed usage, see the [Object Model](https://guides.emberjs.com/release/object-model/)\nsection of the guides.\n\n## Usage with Native Classes\n\nNative JavaScript `class` syntax can be used to extend from any `CoreObject`\nbased class:\n\n```js\nclass Person extends CoreObject {\n  init() {\n    super.init(...arguments);\n    this.name = 'Tomster';\n  }\n}\n```\n\nSome notes about `class` usage:\n\n* `new` syntax is not currently supported with classes that extend from\n  `EmberObject` or `CoreObject`. You must continue to use the `create` method\n  when making new instances of classes, even if they are defined using native\n  class syntax. If you want to use `new` syntax, consider creating classes\n  which do _not_ extend from `EmberObject` or `CoreObject`. Ember features,\n  such as computed properties and decorators, will still work with base-less\n  classes.\n* Instead of using `this._super()`, you must use standard `super` syntax in\n  native classes. See the [MDN docs on classes](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes#Super_class_calls_with_super)\n  for more details.\n* Native classes support using [constructors](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes#Constructor)\n  to set up newly-created instances. Ember uses these to, among other things,\n  support features that need to retrieve other entities by name, like Service\n  injection and `getOwner`. To ensure your custom instance setup logic takes\n  place after this important work is done, avoid using the `constructor` in\n  favor of `init`.\n* Properties passed to `create` will be available on the instance by the time\n  `init` runs, so any code that requires these values should work at that\n  time.\n* Using native classes, and switching back to the old Ember Object model is\n  fully supported.",
       "access": "public",
       "tagname": ""
@@ -3471,7 +3464,7 @@
       "module": "ember",
       "namespace": "Ember",
       "file": "packages/@ember/-internals/views/lib/views/core_view.ts",
-      "line": 6,
+      "line": 7,
       "description": "`Ember.CoreView` is an abstract class that exists to give view-like behavior\nto both Ember's main view class `Component` and other classes that don't need\nthe full functionality of `Component`.\n\nUnless you have specific needs for `CoreView`, you will use `Component`\nin your applications.",
       "extends": "EmberObject",
       "deprecated": true,
@@ -3494,7 +3487,7 @@
       "module": "@ember/application",
       "namespace": "",
       "file": "packages/@ember/application/lib/application.ts",
-      "line": 32,
+      "line": 34,
       "description": "An instance of `Application` is the starting point for every Ember\napplication. It instantiates, initializes and coordinates the\nobjects that make up your app.\n\nEach Ember app has one and only one `Application` object. Although\nEmber CLI creates this object implicitly, the `Application` class\nis defined in the `app/app.js`. You can define a `ready` method on the\n`Application` class, which will be run by Ember when the application is\ninitialized.\n\n```app/app.js\nconst App = Application.extend({\n  ready() {\n    // your code here\n  }\n})\n```\n\nBecause `Application` ultimately inherits from `Ember.Namespace`, any classes\nyou create will have useful string representations when calling `toString()`.\nSee the `Ember.Namespace` documentation for more information.\n\nWhile you can think of your `Application` as a container that holds the\nother classes in your application, there are several other responsibilities\ngoing on under-the-hood that you may want to understand. It is also important\nto understand that an `Application` is different from an `ApplicationInstance`.\nRefer to the Guides to understand the difference between these.\n\n### Event Delegation\n\nEmber uses a technique called _event delegation_. This allows the framework\nto set up a global, shared event listener instead of requiring each view to\ndo it manually. For example, instead of each view registering its own\n`mousedown` listener on its associated element, Ember sets up a `mousedown`\nlistener on the `body`.\n\nIf a `mousedown` event occurs, Ember will look at the target of the event and\nstart walking up the DOM node tree, finding corresponding views and invoking\ntheir `mouseDown` method as it goes.\n\n`Application` has a number of default events that it listens for, as\nwell as a mapping from lowercase events to camel-cased view method names. For\nexample, the `keypress` event causes the `keyPress` method on the view to be\ncalled, the `dblclick` event causes `doubleClick` to be called, and so on.\n\nIf there is a bubbling browser event that Ember does not listen for by\ndefault, you can specify custom events and their corresponding view method\nnames by setting the application's `customEvents` property:\n\n```app/app.js\nimport Application from '@ember/application';\n\nlet App = Application.extend({\n  customEvents: {\n    // add support for the paste event\n    paste: 'paste'\n  }\n});\n```\n\nTo prevent Ember from setting up a listener for a default event,\nspecify the event name with a `null` value in the `customEvents`\nproperty:\n\n```app/app.js\nimport Application from '@ember/application';\n\nlet App = Application.extend({\n  customEvents: {\n    // prevent listeners for mouseenter/mouseleave events\n    mouseenter: null,\n    mouseleave: null\n  }\n});\n```\n\nBy default, the application sets up these event listeners on the document\nbody. However, in cases where you are embedding an Ember application inside\nan existing page, you may want it to set up the listeners on an element\ninside the body.\n\nFor example, if only events inside a DOM element with the ID of `ember-app`\nshould be delegated, set your application's `rootElement` property:\n\n```app/app.js\nimport Application from '@ember/application';\n\nlet App = Application.extend({\n  rootElement: '#ember-app'\n});\n```\n\nThe `rootElement` can be either a DOM element or a CSS selector\nstring. Note that *views appended to the DOM outside the root element will\nnot receive events.* If you specify a custom root element, make sure you only\nappend views inside it!\n\nTo learn more about the events Ember components use, see\n\n[components/handling-events](https://guides.emberjs.com/release/components/handling-events/#toc_event-names).\n\n### Initializers\n\nTo add behavior to the Application's boot process, you can define initializers in\nthe `app/initializers` directory, or with `ember generate initializer` using Ember CLI.\nThese files should export a named `initialize` function which will receive the created `application`\nobject as its first argument.\n\n```javascript\nexport function initialize(application) {\n  // application.inject('route', 'foo', 'service:foo');\n}\n```\n\nApplication initializers can be used for a variety of reasons including:\n\n- setting up external libraries\n- injecting dependencies\n- setting up event listeners in embedded apps\n- deferring the boot process using the `deferReadiness` and `advanceReadiness` APIs.\n\n### Routing\n\nIn addition to creating your application's router, `Application` is\nalso responsible for telling the router when to start routing. Transitions\nbetween routes can be logged with the `LOG_TRANSITIONS` flag, and more\ndetailed intra-transition logging can be logged with\nthe `LOG_TRANSITIONS_INTERNAL` flag:\n\n```javascript\nimport Application from '@ember/application';\n\nlet App = Application.create({\n  LOG_TRANSITIONS: true, // basic logging of successful transitions\n  LOG_TRANSITIONS_INTERNAL: true // detailed logging of all routing steps\n});\n```\n\nBy default, the router will begin trying to translate the current URL into\napplication state once the browser emits the `DOMContentReady` event. If you\nneed to defer routing, you can call the application's `deferReadiness()`\nmethod. Once routing can begin, call the `advanceReadiness()` method.\n\nIf there is any setup required before routing begins, you can implement a\n`ready()` method on your app that will be invoked immediately before routing\nbegins.",
       "extends": "Engine",
       "access": "public",
@@ -3511,7 +3504,7 @@
       "module": "@ember/application",
       "namespace": "",
       "file": "packages/@ember/application/instance.ts",
-      "line": 28,
+      "line": 29,
       "description": "The `ApplicationInstance` encapsulates all of the stateful aspects of a\nrunning `Application`.\n\nAt a high-level, we break application boot into two distinct phases:\n\n* Definition time, where all of the classes, templates, and other\n  dependencies are loaded (typically in the browser).\n* Run time, where we begin executing the application once everything\n  has loaded.\n\nDefinition time can be expensive and only needs to happen once since it is\nan idempotent operation. For example, between test runs and FastBoot\nrequests, the application stays the same. It is only the state that we want\nto reset.\n\nThat state is what the `ApplicationInstance` manages: it is responsible for\ncreating the container that contains all application state, and disposing of\nit once the particular test run or FastBoot request has finished.",
       "access": "public",
       "tagname": "",
@@ -3528,7 +3521,7 @@
       "module": "@ember/application",
       "namespace": "ApplicationInstance",
       "file": "packages/@ember/application/instance.ts",
-      "line": 325,
+      "line": 326,
       "description": "A list of boot-time configuration options for customizing the behavior of\nan `ApplicationInstance`.\n\nThis is an interface class that exists purely to document the available\noptions; you do not need to construct it manually. Simply pass a regular\nJavaScript object containing the desired options into methods that require\none of these options object:\n\n```javascript\nMyApp.visit(\"/\", { location: \"none\", rootElement: \"#container\" });\n```\n\nNot all combinations of the supported options are valid. See the documentation\non `Application#visit` for the supported configurations.\n\nInternal, experimental or otherwise unstable flags are marked as private.",
       "access": "public",
       "tagname": ""
@@ -3625,7 +3618,7 @@
       "module": "@ember/engine",
       "namespace": "",
       "file": "packages/@ember/engine/index.ts",
-      "line": 39,
+      "line": 40,
       "description": "The `Engine` class contains core functionality for both applications and\nengines.\n\nEach engine manages a registry that's used for dependency injection and\nexposed through `RegistryProxy`.\n\nEngines also manage initializers and instance initializers.\n\nEngines can spawn `EngineInstance` instances via `buildInstance()`.",
       "extends": "Ember.Namespace",
       "uses": [
@@ -3782,7 +3775,7 @@
       "module": "@ember/service",
       "namespace": "",
       "file": "packages/@ember/service/index.ts",
-      "line": 90,
+      "line": 87,
       "extends": "EmberObject",
       "since": "1.10.0",
       "access": "public",
@@ -3815,7 +3808,7 @@
       "module": "@ember/test",
       "namespace": "",
       "file": "packages/ember-testing/lib/adapters/adapter.js",
-      "line": 11,
+      "line": 7,
       "description": "The primary purpose of this class is to create hooks that can be implemented\nby an adapter for various test frameworks.",
       "access": "public",
       "tagname": ""
@@ -4483,7 +4476,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/container.ts",
-      "line": 91,
+      "line": 93,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -4495,7 +4488,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/container.ts",
-      "line": 98,
+      "line": 100,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -4506,7 +4499,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/container.ts",
-      "line": 104,
+      "line": 106,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -4517,7 +4510,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/container.ts",
-      "line": 110,
+      "line": 112,
       "description": "Given a fullName return a corresponding instance.\n The default behavior is for lookup to return a singleton instance.\nThe singleton is scoped to the container, allowing multiple containers\nto all have their own locally scoped singletons.\n ```javascript\nlet registry = new Registry();\nlet container = registry.container();\n registry.register('api:twitter', Twitter);\n let twitter = container.lookup('api:twitter');\n twitter instanceof Twitter; // => true\n // by default the container will return singletons\nlet twitter2 = container.lookup('api:twitter');\ntwitter2 instanceof Twitter; // => true\n twitter === twitter2; //=> true\n```\n If singletons are not wanted, an optional flag can be provided at lookup.\n ```javascript\nlet registry = new Registry();\nlet container = registry.container();\n registry.register('api:twitter', Twitter);\n let twitter = container.lookup('api:twitter', { singleton: false });\nlet twitter2 = container.lookup('api:twitter', { singleton: false });\n twitter === twitter2; //=> false\n```",
       "access": "private",
       "tagname": "",
@@ -4545,7 +4538,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/container.ts",
-      "line": 149,
+      "line": 151,
       "description": "A depth first traversal, destroying the container, its descendant containers and all\ntheir managed objects.",
       "access": "private",
       "tagname": "",
@@ -4556,7 +4549,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/container.ts",
-      "line": 166,
+      "line": 168,
       "description": "Clear either the entire cache or just the cache for a particular key.",
       "access": "private",
       "tagname": "",
@@ -4574,7 +4567,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/container.ts",
-      "line": 183,
+      "line": 185,
       "description": "Returns an object that can be used to provide an owner to a\nmanually created instance.",
       "access": "private",
       "tagname": "",
@@ -4589,7 +4582,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/container.ts",
-      "line": 196,
+      "line": 198,
       "description": "Given a fullName, return the corresponding factory. The consumer of the factory\nis responsible for the destruction of any factory instances, as there is no\nway for the container to ensure instances are destroyed when it itself is\ndestroyed.",
       "access": "public",
       "tagname": "",
@@ -4611,7 +4604,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 95,
+      "line": 96,
       "description": "A backup registry for resolving registrations when no matches can be found.",
       "access": "private",
       "tagname": "",
@@ -4623,7 +4616,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 103,
+      "line": 104,
       "description": "An object that has a `resolve` method that resolves a name.",
       "access": "private",
       "tagname": "",
@@ -4635,7 +4628,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 111,
+      "line": 112,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -4646,7 +4639,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 117,
+      "line": 118,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -4657,7 +4650,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 124,
+      "line": 125,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -4668,7 +4661,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 131,
+      "line": 132,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -4679,7 +4672,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 138,
+      "line": 139,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -4690,7 +4683,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 145,
+      "line": 146,
       "description": "Creates a container based on this registry.",
       "access": "private",
       "tagname": "",
@@ -4712,7 +4705,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 157,
+      "line": 158,
       "description": "Registers a factory for later injection.\n\nExample:\n\n```javascript\nlet registry = new Registry();\n\nregistry.register('model:user', Person, {singleton: false });\nregistry.register('fruit:favorite', Orange);\nregistry.register('communication:main', Email, {singleton: false});\n```",
       "access": "private",
       "tagname": "",
@@ -4740,7 +4733,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 194,
+      "line": 195,
       "description": "Unregister a fullName\n\n```javascript\nlet registry = new Registry();\nregistry.register('model:user', User);\n\nregistry.resolve('model:user').create() instanceof User //=> true\n\nregistry.unregister('model:user')\nregistry.resolve('model:user') === undefined //=> true\n```",
       "access": "private",
       "tagname": "",
@@ -4758,7 +4751,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 222,
+      "line": 223,
       "description": "Given a fullName return the corresponding factory.\n\nBy default `resolve` will retrieve the factory from\nthe registry.\n\n```javascript\nlet registry = new Registry();\nregistry.register('api:twitter', Twitter);\n\nregistry.resolve('api:twitter') // => Twitter\n```\n\nOptionally the registry can be provided with a custom resolver.\nIf provided, `resolve` will first provide the custom resolver\nthe opportunity to resolve the fullName, otherwise it will fallback\nto the registry.\n\n```javascript\nlet registry = new Registry();\nregistry.resolver = function(fullName) {\n   // lookup via the module system of choice\n };\n\n// the twitter factory is added to the module system\nregistry.resolve('api:twitter') // => Twitter\n```",
       "access": "private",
       "tagname": "",
@@ -4780,7 +4773,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 263,
+      "line": 264,
       "description": "A hook that can be used to describe how the resolver will\nattempt to find the factory.\n\nFor example, the default Ember `.describe` returns the full\nclass name (including namespace) where Ember's resolver expects\nto find the `fullName`.",
       "access": "private",
       "tagname": "",
@@ -4802,7 +4795,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 286,
+      "line": 287,
       "description": "A hook to enable custom fullName normalization behavior",
       "access": "private",
       "tagname": "",
@@ -4824,7 +4817,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 304,
+      "line": 305,
       "description": "Normalize a fullName based on the application's conventions",
       "access": "private",
       "tagname": "",
@@ -4846,7 +4839,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 319,
+      "line": 320,
       "itemtype": "method",
       "name": "makeToString",
       "access": "private",
@@ -4872,7 +4865,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 337,
+      "line": 338,
       "description": "Given a fullName check if the container is aware of its factory\nor singleton instance.",
       "access": "private",
       "tagname": "",
@@ -4908,7 +4901,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 356,
+      "line": 357,
       "description": "Allow registering options for all factories of a type.\n\n```javascript\nlet registry = new Registry();\nlet container = registry.container();\n\n// if all of type `connection` must not be singletons\nregistry.optionsForType('connection', { singleton: false });\n\nregistry.register('connection:twitter', TwitterConnection);\nregistry.register('connection:facebook', FacebookConnection);\n\nlet twitter = container.lookup('connection:twitter');\nlet twitter2 = container.lookup('connection:twitter');\n\ntwitter === twitter2; // => false\n\nlet facebook = container.lookup('connection:facebook');\nlet facebook2 = container.lookup('connection:facebook');\n\nfacebook === facebook2; // => false\n```",
       "access": "private",
       "tagname": "",
@@ -4931,7 +4924,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 397,
+      "line": 398,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -4953,14 +4946,14 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 440,
+      "line": 441,
       "description": "This is deprecated in favor of explicit injection of dependencies.\n\nReference: https://deprecations.emberjs.com/v3.x#toc_implicit-injections\n```\n\n@private\n@method injection\n@param {String} factoryName\n@param {String} property\n@param {String} injectionName\n@deprecated",
       "class": "Registry",
       "module": "rsvp"
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 470,
+      "line": 471,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -5081,7 +5074,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/container_debug_adapter.ts",
-      "line": 57,
+      "line": 53,
       "description": "The resolver instance of the application\nbeing debugged. This property will be injected\non creation.",
       "itemtype": "property",
       "name": "resolver",
@@ -5092,7 +5085,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/container_debug_adapter.ts",
-      "line": 67,
+      "line": 63,
       "description": "Returns true if it is possible to catalog a list of available\nclasses in the resolver for a given type.",
       "itemtype": "method",
       "name": "canCatalogEntriesByType",
@@ -5114,7 +5107,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/container_debug_adapter.ts",
-      "line": 84,
+      "line": 80,
       "description": "Returns the available classes a given type.",
       "itemtype": "method",
       "name": "catalogEntriesByType",
@@ -5136,7 +5129,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 214,
+      "line": 212,
       "description": "The container-debug-adapter which is used\nto list all models.",
       "itemtype": "property",
       "name": "containerDebugAdapter",
@@ -5149,7 +5142,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 224,
+      "line": 222,
       "description": "The number of attributes to send\nas columns. (Enough to make the record\nidentifiable).",
       "access": "private",
       "tagname": "",
@@ -5162,7 +5155,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 236,
+      "line": 234,
       "description": "Ember Data > v1.0.0-beta.18\nrequires string model names to be passed\naround instead of the actual factories.\n\nThis is a stamp for the Ember Inspector\nto differentiate between the versions\nto be able to support older versions too.",
       "access": "public",
       "tagname": "",
@@ -5173,7 +5166,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 250,
+      "line": 248,
       "description": "Map from records arrays to RecordsWatcher instances",
       "access": "private",
       "tagname": "",
@@ -5185,7 +5178,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 258,
+      "line": 256,
       "description": "Map from records arrays to TypeWatcher instances",
       "access": "private",
       "tagname": "",
@@ -5197,7 +5190,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 266,
+      "line": 264,
       "description": "Callback that is currently scheduled on backburner end to flush and check\nall active watchers.",
       "access": "private",
       "tagname": "",
@@ -5209,7 +5202,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 276,
+      "line": 274,
       "description": "Stores all methods that clear observers.\nThese methods will be called on destruction.",
       "access": "private",
       "tagname": "",
@@ -5221,7 +5214,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 285,
+      "line": 283,
       "description": "Specifies how records can be filtered.\nRecords returned will need to have a `filterValues`\nproperty with a key for every name in the returned array.",
       "access": "public",
       "tagname": "",
@@ -5236,7 +5229,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 299,
+      "line": 297,
       "description": "Fetch the model types and observe them for changes.",
       "access": "public",
       "tagname": "",
@@ -5263,7 +5256,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 347,
+      "line": 345,
       "description": "Fetch the records of a given type and observe them for changes.",
       "access": "public",
       "tagname": "",
@@ -5300,7 +5293,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 419,
+      "line": 417,
       "description": "Clear all observers before destruction",
       "access": "private",
       "tagname": "",
@@ -5311,7 +5304,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 437,
+      "line": 435,
       "description": "Detect whether a class is a model.\n\nTest that against the model class\nof your persistence library.",
       "access": "public",
       "tagname": "",
@@ -5325,7 +5318,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 451,
+      "line": 449,
       "description": "Get the columns for a given model type.",
       "access": "public",
       "tagname": "",
@@ -5340,7 +5333,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 464,
+      "line": 462,
       "description": "Adds observers to a model type class.",
       "access": "private",
       "tagname": "",
@@ -5367,7 +5360,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 501,
+      "line": 499,
       "description": "Wraps a given model type and observes changes to it.",
       "access": "private",
       "tagname": "",
@@ -5394,7 +5387,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 525,
+      "line": 523,
       "description": "Fetches all models defined in the application.",
       "access": "private",
       "tagname": "",
@@ -5409,7 +5402,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 550,
+      "line": 548,
       "description": "Loops over all namespaces and all objects\nattached to them.",
       "access": "private",
       "tagname": "",
@@ -5424,7 +5417,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 579,
+      "line": 577,
       "description": "Fetches all loaded records for a given type.",
       "access": "public",
       "tagname": "",
@@ -5439,7 +5432,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 592,
+      "line": 590,
       "description": "Wraps a record and observers changes to it.",
       "access": "private",
       "tagname": "",
@@ -5461,7 +5454,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 612,
+      "line": 610,
       "description": "Gets the values for each column.",
       "access": "public",
       "tagname": "",
@@ -5476,7 +5469,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 624,
+      "line": 622,
       "description": "Returns keywords to match when searching records.",
       "access": "public",
       "tagname": "",
@@ -5491,7 +5484,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 635,
+      "line": 633,
       "description": "Returns the values of filters defined by `getFilters`.",
       "access": "public",
       "tagname": "",
@@ -5513,7 +5506,7 @@
     },
     {
       "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
-      "line": 647,
+      "line": 645,
       "description": "Each record can have a color that represents its state.",
       "access": "public",
       "tagname": "",
@@ -5535,7 +5528,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/components/abstract-input.ts",
-      "line": 125,
+      "line": 127,
       "description": "The `change` and `input` actions need to be overridden in the `Input`\nsubclass. Unfortunately, some ember-source builds currently uses babel\nloose mode to transpile its classes. Having the `@action` decorator on the\nsuper class creates a getter on the prototype, and when the subclass\noverrides the method, the loose mode transpilation would emit something\nlike `Subclass.prototype['change'] = function change() { ... }`, which\nfails because `prototype['change']` is getter-only/readonly. The correct\nsolution is to use `Object.defineProperty(prototype, 'change', ...)` but\nthat requires disabling loose mode. For now, the workaround is to add the\ndecorator only on the subclass. This is more of a configuration issue on\nour own builds and doesn't really affect apps.",
       "class": "Ember.Templates.helpers",
       "module": "@ember/debug"
@@ -5610,14 +5603,14 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/components/internal.ts",
-      "line": 37,
+      "line": 39,
       "description": "The default HTML id attribute. We don't really _need_ one, this is just\nadded for compatibility as it's hard to tell if people rely on it being\npresent, and it doens't really hurt.\n\nHowever, don't rely on this internally, like passing it to `getElementId`.\nThis can be (and often is) overriden by passing an `id` attribute on the\ninvocation, which shadows this default id via `...attributes`.",
       "class": "Ember.Templates.components",
       "module": "@ember/component"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/components/internal.ts",
-      "line": 50,
+      "line": 52,
       "description": "The default HTML class attribute. Similar to the above, we don't _need_\nthem, they are just added for compatibility as it's similarly hard to tell\nif people rely on it in their CSS etc, and it doens't really hurt.",
       "class": "Ember.Templates.components",
       "module": "@ember/component"
@@ -5709,7 +5702,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/helpers/action.ts",
-      "line": 23,
+      "line": 18,
       "description": "The `{{action}}` helper provides a way to pass triggers for behavior (usually\njust a function) between components, and into components from controllers.\n\n### Passing functions with the action helper\n\nThere are three contexts an action helper can be used in. The first two\ncontexts to discuss are attribute context, and Handlebars value context.\n\n```handlebars\n{{! An example of attribute context }}\n<div onclick={{action \"save\"}}></div>\n{{! Examples of Handlebars value context }}\n{{input on-input=(action \"save\")}}\n{{yield (action \"refreshData\") andAnotherParam}}\n```\n\nIn these contexts,\nthe helper is called a \"closure action\" helper. Its behavior is simple:\nIf passed a function name, read that function off the `actions` property\nof the current context. Once that function is read, or immediately if a function was\npassed, create a closure over that function and any arguments.\nThe resulting value of an action helper used this way is simply a function.\n\nFor example, in the attribute context:\n\n```handlebars\n{{! An example of attribute context }}\n<div onclick={{action \"save\"}}></div>\n```\n\nThe resulting template render logic would be:\n\n```js\nvar div = document.createElement('div');\nvar actionFunction = (function(context){\n  return function() {\n    return context.actions.save.apply(context, arguments);\n  };\n})(context);\ndiv.onclick = actionFunction;\n```\n\nThus when the div is clicked, the action on that context is called.\nBecause the `actionFunction` is just a function, closure actions can be\npassed between components and still execute in the correct context.\n\nHere is an example action handler on a component:\n\n```app/components/my-component.js\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n\nexport default class extends Component {\n  @action\n  save() {\n    this.model.save();\n  }\n}\n```\n\nActions are always looked up on the `actions` property of the current context.\nThis avoids collisions in the naming of common actions, such as `destroy`.\nTwo options can be passed to the `action` helper when it is used in this way.\n\n* `target=someProperty` will look to `someProperty` instead of the current\n  context for the `actions` hash. This can be useful when targeting a\n  service for actions.\n* `value=\"target.value\"` will read the path `target.value` off the first\n  argument to the action when it is called and rewrite the first argument\n  to be that value. This is useful when attaching actions to event listeners.\n\n### Invoking an action\n\nClosure actions curry both their scope and any arguments. When invoked, any\nadditional arguments are added to the already curried list.\nActions are presented in JavaScript as callbacks, and are\ninvoked like any other JavaScript function.\n\nFor example\n\n```app/components/update-name.js\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n\nexport default class extends Component {\n  @action\n  setName(model, name) {\n    model.set('name', name);\n  }\n}\n```\n\n```app/components/update-name.hbs\n{{input on-input=(action (action 'setName' @model) value=\"target.value\")}}\n```\n\nThe first argument (`@model`) was curried over, and the run-time argument (`event`)\nbecomes a second argument. Action calls can be nested this way because each simply\nreturns a function. Any function can be passed to the `{{action}}` helper, including\nother actions.\n\nActions invoked with `sendAction` have the same currying behavior as demonstrated\nwith `on-input` above. For example:\n\n```app/components/my-input.js\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n\nexport default class extends Component {\n  @action\n  setName(model, name) {\n    model.set('name', name);\n  }\n}\n```\n\n```handlebars\n<MyInput @submit={{action 'setName' @model}} />\n```\n\nor\n\n```handlebars\n{{my-input submit=(action 'setName' @model)}}\n```\n\n```app/components/my-component.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  click() {\n    // Note that model is not passed, it was curried in the template\n    this.submit('bob');\n  }\n});\n```\n\n### Attaching actions to DOM elements\n\nThe third context of the `{{action}}` helper can be called \"element space\".\nFor example:\n\n```handlebars\n{{! An example of element space }}\n<div {{action \"save\"}}></div>\n```\n\nUsed this way, the `{{action}}` helper provides a useful shortcut for\nregistering an HTML element in a template for a single DOM event and\nforwarding that interaction to the template's context (controller or component).\nIf the context of a template is a controller, actions used this way will\nbubble to routes when the controller does not implement the specified action.\nOnce an action hits a route, it will bubble through the route hierarchy.\n\n### Event Propagation\n\n`{{action}}` helpers called in element space can control event bubbling. Note\nthat the closure style actions cannot.\n\nEvents triggered through the action helper will automatically have\n`.preventDefault()` called on them. You do not need to do so in your event\nhandlers. If you need to allow event propagation (to handle file inputs for\nexample) you can supply the `preventDefault=false` option to the `{{action}}` helper:\n\n```handlebars\n<div {{action \"sayHello\" preventDefault=false}}>\n  <input type=\"file\" />\n  <input type=\"checkbox\" />\n</div>\n```\n\nTo disable bubbling, pass `bubbles=false` to the helper:\n\n```handlebars\n<button {{action 'edit' post bubbles=false}}>Edit</button>\n```\n\nTo disable bubbling with closure style actions you must create your own\nwrapper helper that makes use of `event.stopPropagation()`:\n\n```handlebars\n<div onclick={{disable-bubbling (action \"sayHello\")}}>Hello</div>\n```\n\n```app/helpers/disable-bubbling.js\nimport { helper } from '@ember/component/helper';\n\nexport function disableBubbling([action]) {\n  return function(event) {\n    event.stopPropagation();\n    return action(event);\n  };\n}\nexport default helper(disableBubbling);\n```\n\nIf you need the default handler to trigger you should either register your\nown event handler, or use event methods on your view class. See\n[\"Responding to Browser Events\"](/ember/release/classes/Component)\nin the documentation for `Component` for more information.\n\n### Specifying DOM event type\n\n`{{action}}` helpers called in element space can specify an event type.\nBy default the `{{action}}` helper registers for DOM `click` events. You can\nsupply an `on` option to the helper to specify a different DOM event name:\n\n```handlebars\n<div {{action \"anActionName\" on=\"doubleClick\"}}>\n  click me\n</div>\n```\n\nSee [\"Event Names\"](/ember/release/classes/Component) for a list of\nacceptable DOM event names.\n\n### Specifying whitelisted modifier keys\n\n`{{action}}` helpers called in element space can specify modifier keys.\nBy default the `{{action}}` helper will ignore click events with pressed modifier\nkeys. You can supply an `allowedKeys` option to specify which keys should not be ignored.\n\n```handlebars\n<div {{action \"anActionName\" allowedKeys=\"alt\"}}>\n  click me\n</div>\n```\n\nThis way the action will fire when clicking with the alt key pressed down.\nAlternatively, supply \"any\" to the `allowedKeys` option to accept any combination of modifier keys.\n\n```handlebars\n<div {{action \"anActionName\" allowedKeys=\"any\"}}>\n  click me with any key pressed\n</div>\n```\n\n### Specifying a Target\n\nA `target` option can be provided to the helper to change\nwhich object will receive the method call. This option must be a path\nto an object, accessible in the current context:\n\n```app/templates/application.hbs\n<div {{action \"anActionName\" target=someService}}>\n  click me\n</div>\n```\n\n```app/controllers/application.js\nimport Controller from '@ember/controller';\nimport { service } from '@ember/service';\n\nexport default class extends Controller {\n  @service someService;\n}\n```",
       "itemtype": "method",
       "name": "action",
@@ -5990,7 +5983,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/syntax/mount.ts",
-      "line": 13,
+      "line": 16,
       "description": "The `{{mount}}` helper lets you embed a routeless engine in a template.\nMounting an engine will cause an instance to be booted and its `application`\ntemplate to be rendered.\n\nFor example, the following template mounts the `ember-chat` engine:\n\n```handlebars\n{{! application.hbs }}\n{{mount \"ember-chat\"}}\n```\n\nAdditionally, you can also pass in a `model` argument that will be\nset as the engines model. This can be an existing object:\n\n```\n<div>\n  {{mount 'admin' model=userSettings}}\n</div>\n```\n\nOr an inline `hash`, and you can even pass components:\n\n```\n<div>\n  <h1>Application template!</h1>\n  {{mount 'admin' model=(hash\n      title='Secret Admin'\n      signInButton=(component 'sign-in-button')\n  )}}\n</div>\n```",
       "itemtype": "method",
       "name": "mount",
@@ -6014,7 +6007,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/syntax/outlet.ts",
-      "line": 19,
+      "line": 22,
       "description": "The `{{outlet}}` helper lets you specify where a child route will render in\nyour template. An important use of the `{{outlet}}` helper is in your\napplication's `application.hbs` file:\n\n```app/templates/application.hbs\n<MyHeader />\n\n<div class=\"my-dynamic-content\">\n  <!-- this content will change based on the current route, which depends on the current URL -->\n  {{outlet}}\n</div>\n\n<MyFooter />\n```\n\nSee the [routing guide](https://guides.emberjs.com/release/routing/rendering-a-template/) for more\ninformation on how your `route` interacts with the `{{outlet}}` helper.\nNote: Your content __will not render__ if there isn't an `{{outlet}}` for it.",
       "itemtype": "method",
       "name": "outlet",
@@ -6116,7 +6109,7 @@
     {
       "file": "packages/@ember/-internals/glimmer/lib/utils/string.ts",
       "line": 61,
-      "description": "Mark a string as safe for unescaped output with Ember templates. If you\nreturn HTML from a helper, use this function to\nensure Ember's rendering layer does not escape the HTML.\n\n```javascript\nimport { htmlSafe } from '@ember/template';\n\nhtmlSafe('<div>someString</div>')\n```",
+      "description": "Use this method to indicate that a string should be rendered as HTML\nwhen the string is used in a template. To say this another way,\nstrings marked with `htmlSafe` will not be HTML escaped.\n\nA word of warning -   The `htmlSafe` method does not make the string safe;\nit only tells the framework to treat the string as if it is safe to render\nas HTML. If a string contains user inputs or other untrusted\ndata, you must sanitize the string before using the `htmlSafe` method.\nOtherwise your code is vulnerable to\n[Cross-Site Scripting](https://owasp.org/www-community/attacks/DOM_Based_XSS).\nThere are many open source sanitization libraries to choose from,\nboth for front end and server-side sanitization.\n\n```javascript\nimport { htmlSafe } from '@ember/template';\n\nconst someTrustedOrSanitizedString = \"<div>Hello!</div>\"\n\nhtmlSafe(someTrustedorSanitizedString)\n```",
       "itemtype": "method",
       "name": "htmlSafe",
       "static": 1,
@@ -6131,7 +6124,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/utils/string.ts",
-      "line": 87,
+      "line": 98,
       "description": "Detects if a string was decorated using `htmlSafe`.\n\n```javascript\nimport { htmlSafe, isHTMLSafe } from '@ember/template';\n\nvar plainString = 'plain string',\n    safeString = htmlSafe('<div>someValue</div>');\n\nisHTMLSafe(plainString); // false\nisHTMLSafe(safeString);  // true\n```",
       "itemtype": "method",
       "name": "isHTMLSafe",
@@ -6147,19 +6140,19 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/views/outlet.ts",
-      "line": 109,
+      "line": 111,
       "class": "Component",
       "module": "@ember/template"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/views/outlet.ts",
-      "line": 117,
+      "line": 119,
       "class": "Component",
       "module": "@ember/template"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 655,
+      "line": 656,
       "description": "Called when the attributes passed into the component have been updated.\n Called both during the initial render of a container and during a rerender.\n Can be used in place of an observer; code placed here will be executed\n every time any attribute updates.",
       "itemtype": "method",
       "name": "didReceiveAttrs",
@@ -6171,7 +6164,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 666,
+      "line": 667,
       "description": "Called when the attributes passed into the component have been updated.\n Called both during the initial render of a container and during a rerender.\n Can be used in place of an observer; code placed here will be executed\n every time any attribute updates.",
       "itemtype": "event",
       "name": "didReceiveAttrs",
@@ -6183,7 +6176,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 676,
+      "line": 677,
       "description": "Called after a component has been rendered, both on initial render and\n in subsequent rerenders.",
       "itemtype": "method",
       "name": "didRender",
@@ -6195,7 +6188,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 685,
+      "line": 686,
       "description": "Called after a component has been rendered, both on initial render and\n in subsequent rerenders.",
       "itemtype": "event",
       "name": "didRender",
@@ -6207,7 +6200,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 693,
+      "line": 694,
       "description": "Called before a component has been rendered, both on initial render and\n in subsequent rerenders.",
       "itemtype": "method",
       "name": "willRender",
@@ -6219,7 +6212,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 702,
+      "line": 703,
       "description": "Called before a component has been rendered, both on initial render and\n in subsequent rerenders.",
       "itemtype": "event",
       "name": "willRender",
@@ -6231,7 +6224,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 710,
+      "line": 711,
       "description": "Called when the attributes passed into the component have been changed.\n Called only during a rerender, not during an initial render.",
       "itemtype": "method",
       "name": "didUpdateAttrs",
@@ -6243,7 +6236,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 719,
+      "line": 720,
       "description": "Called when the attributes passed into the component have been changed.\n Called only during a rerender, not during an initial render.",
       "itemtype": "event",
       "name": "didUpdateAttrs",
@@ -6255,7 +6248,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 727,
+      "line": 728,
       "description": "Called when the component is about to update and rerender itself.\n Called only during a rerender, not during an initial render.",
       "itemtype": "method",
       "name": "willUpdate",
@@ -6267,7 +6260,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 736,
+      "line": 737,
       "description": "Called when the component is about to update and rerender itself.\n Called only during a rerender, not during an initial render.",
       "itemtype": "event",
       "name": "willUpdate",
@@ -6279,7 +6272,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 744,
+      "line": 745,
       "description": "Called when the component has updated and rerendered itself.\n Called only during a rerender, not during an initial render.",
       "itemtype": "method",
       "name": "didUpdate",
@@ -6291,7 +6284,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 753,
+      "line": 754,
       "description": "Called when the component has updated and rerendered itself.\n Called only during a rerender, not during an initial render.",
       "itemtype": "event",
       "name": "didUpdate",
@@ -6303,7 +6296,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 761,
+      "line": 762,
       "description": "The HTML `id` of the component's element in the DOM. You can provide this\nvalue yourself but it must be unique (just as in HTML):\n\n```handlebars\n{{my-component elementId=\"a-really-cool-id\"}}\n```\n\n```handlebars\n<MyComponent @elementId=\"a-really-cool-id\" />\n```\nIf not manually set a default value will be provided by the framework.\nOnce rendered an element's `elementId` is considered immutable and you\nshould never change it. If you need to compute a dynamic value for the\n`elementId`, you should do this when the component or element is being\ninstantiated:\n\n```javascript\nexport default Component.extend({\n  init() {\n    this._super(...arguments);\n\n    var index = this.get('index');\n    this.set('elementId', `component-id${index}`);\n  }\n});\n```",
       "itemtype": "property",
       "name": "elementId",
@@ -6315,7 +6308,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 950,
+      "line": 951,
       "description": "Normally, Ember's component model is \"write-only\". The component takes a\nbunch of attributes that it got passed in, and uses them to render its\ntemplate.\n\nOne nice thing about this model is that if you try to set a value to the\nsame thing as last time, Ember (through HTMLBars) will avoid doing any\nwork on the DOM.\n\nThis is not just a performance optimization. If an attribute has not\nchanged, it is important not to clobber the element's \"hidden state\".\nFor example, if you set an input's `value` to the same value as before,\nit will clobber selection state and cursor position. In other words,\nsetting an attribute is not **always** idempotent.\n\nThis method provides a way to read an element's attribute and also\nupdate the last value Ember knows about at the same time. This makes\nsetting an attribute idempotent.\n\nIn particular, what this means is that if you get an `<input>` element's\n`value` attribute and then re-render the template with the same value,\nit will avoid clobbering the cursor and selection position.\nSince most attribute sets are idempotent in the browser, you typically\ncan get away with reading attributes using jQuery, but the most reliable\nway to do so is through this method.",
       "itemtype": "method",
       "name": "readDOMAttr",
@@ -6336,7 +6329,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 1010,
+      "line": 1011,
       "description": "Layout can be used to wrap content in a component.",
       "itemtype": "property",
       "name": "layout",
@@ -6348,7 +6341,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 1018,
+      "line": 1019,
       "description": "The name of the layout to lookup if no layout is provided.\nBy default `Component` will lookup a template with this name in\n`Ember.TEMPLATES` (a shared global object).",
       "itemtype": "property",
       "name": "layoutName",
@@ -6361,7 +6354,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 1029,
+      "line": 1030,
       "description": "The WAI-ARIA role of the control represented by this view. For example, a\n button may have a role of type 'button', or a pane may have a role of\n type 'alertdialog'. This property is used by assistive software to help\n visually challenged users navigate rich web applications.\n\n The full list of valid WAI-ARIA roles is available at:\n [https://www.w3.org/TR/wai-aria/#roles_categorization](https://www.w3.org/TR/wai-aria/#roles_categorization)",
       "itemtype": "property",
       "name": "ariaRole",
@@ -6374,7 +6367,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 1054,
+      "line": 1055,
       "description": "Enables components to take a list of parameters as arguments.\n For example, a component that takes two parameters with the names\n `name` and `age`:\n\n ```app/components/my-component.js\n import Component from '@ember/component';\n\n let MyComponent = Component.extend();\n\n MyComponent.reopenClass({\n   positionalParams: ['name', 'age']\n });\n\n export default MyComponent;\n ```\n\n It can then be invoked like this:\n\n ```hbs\n {{my-component \"John\" 38}}\n ```\n\n The parameters can be referred to just like named parameters:\n\n ```hbs\n Name: {{name}}, Age: {{age}}.\n ```\n\n Using a string instead of an array allows for an arbitrary number of\n parameters:\n\n ```app/components/my-component.js\n import Component from '@ember/component';\n\n let MyComponent = Component.extend();\n\n MyComponent.reopenClass({\n   positionalParams: 'names'\n });\n\n export default MyComponent;\n ```\n\n It can then be invoked like this:\n\n ```hbs\n {{my-component \"John\" \"Michael\" \"Scott\"}}\n ```\n The parameters can then be referred to by enumerating over the list:\n\n ```hbs\n {{#each names as |name|}}{{name}}{{/each}}\n ```",
       "static": 1,
       "access": "public",
@@ -6387,7 +6380,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/glimmer-tracking-docs.ts",
-      "line": 14,
+      "line": 22,
       "description": "Marks a property as tracked. By default, values that are rendered in Ember app\ntemplates are _static_, meaning that updates to them won't cause the\napplication to rerender. Marking a property as tracked means that when that\nproperty changes, any templates that used that property, directly or\nindirectly, will rerender. For instance, consider this component:\n\n```handlebars\n<div>Count: {{this.count}}</div>\n<div>Times Ten: {{this.timesTen}}</div>\n<div>\n  <button {{on \"click\" this.plusOne}}>\n    Plus One\n  </button>\n</div>\n```\n\n```javascript\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\nimport { action } from '@ember/object';\n\nexport default class CounterComponent extends Component {\n  @tracked count = 0;\n\n  get timesTen() {\n    return this.count * 10;\n  }\n\n  @action\n  plusOne() {\n    this.count += 1;\n  }\n}\n```\n\nBoth the `{{this.count}}` and the `{{this.timesTen}}` properties in the\ntemplate will update whenever the button is clicked. Any tracked properties\nthat are used in any way to calculate a value that is used in the template\nwill cause a rerender when updated - this includes through method calls and\nother means:\n\n```javascript\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\n\nclass Entry {\n  @tracked name;\n  @tracked phoneNumber;\n\n  constructor(name, phoneNumber) {\n    this.name = name;\n    this.phoneNumber = phoneNumber;\n  }\n}\n\nexport default class PhoneBookComponent extends Component {\n  entries = [\n    new Entry('Pizza Palace', 5551234),\n    new Entry('1st Street Cleaners', 5554321),\n    new Entry('Plants R Us', 5552468),\n  ];\n\n  // Any usage of this property will update whenever any of the names in the\n  // entries arrays are updated\n  get names() {\n    return this.entries.map(e => e.name);\n  }\n\n  // Any usage of this property will update whenever any of the numbers in the\n  // entries arrays are updated\n  get numbers() {\n    return this.getFormattedNumbers();\n  }\n\n  getFormattedNumbers() {\n    return this.entries\n      .map(e => e.phoneNumber)\n      .map(number => {\n        let numberString = '' + number;\n\n        return numberString.slice(0, 3) + '-' + numberString.slice(3);\n      });\n  }\n}\n```\n\nIt's important to note that setting tracked properties will always trigger an\nupdate, even if the property is set to the same value as it was before.\n\n```js\nlet entry = new Entry('Pizza Palace', 5551234);\n\n// if entry was used when rendering, this would cause a rerender, even though\n// the name is being set to the same value as it was before\nentry.name = entry.name;\n```\n\n`tracked` can also be used with the classic Ember object model in a similar\nmanner to classic computed properties:\n\n```javascript\nimport EmberObject from '@ember/object';\nimport { tracked } from '@glimmer/tracking';\n\nconst Entry = EmberObject.extend({\n  name: tracked(),\n  phoneNumber: tracked()\n});\n```\n\nOften this is unnecessary, but to ensure robust auto-tracking behavior it is\nadvisable to mark tracked state appropriately wherever possible.\n\nThis form of `tracked` also accepts an optional configuration object\ncontaining either an initial `value` or an `initializer` function (but not\nboth).\n\n```javascript\nimport EmberObject from '@ember/object';\nimport { tracked } from '@glimmer/tracking';\n\nconst Entry = EmberObject.extend({\n  name: tracked({ value: 'Zoey' }),\n  favoriteSongs: tracked({\n    initializer: () => ['Raspberry Beret', 'Time After Time']\n  })\n});\n```",
       "itemtype": "method",
       "name": "tracked",
@@ -6397,9 +6390,21 @@
       "class": "@glimmer/tracking",
       "module": "@glimmer/tracking"
     },
+    {
+      "file": "packages/@ember/-internals/glimmer/lib/glimmer-tracking-docs.ts",
+      "line": 158,
+      "description": "Gives the getter a caching behavior. The return value of the getter\nwill be cached until any of the properties it is entangled with\nare invalidated. This is useful when a getter is expensive and\nused very often.\n\nFor instance, in this GuestList class, we have the sortedGuests\ngetter that sorts the guests alphabetically:\n\n```javascript\n  import { tracked } from '@glimmer/tracking';\n\n  class GuestList {\n    @tracked guests = ['Zoey', 'Tomster'];\n\n    get sortedGuests() {\n      return this.guests.slice().sort()\n    }\n  }\n```\n\nEvery time sortedGuests is accessed, a new array will be created and sorted,\nbecause JavaScript getters do not cache by default. When the guest list\nis small, like the one in the example, this is not a problem. However, if\nthe guest list were to grow very large, it would mean that we would be doing\na large amount of work each time we accessed sortedGetters. With @cached,\nwe can cache the value instead:\n\n```javascript\n  import { tracked, cached } from '@glimmer/tracking';\n\n  class GuestList {\n    @tracked guests = ['Zoey', 'Tomster'];\n\n    @cached\n    get sortedGuests() {\n      return this.guests.slice().sort()\n    }\n  }\n```\n\nNow the sortedGuests getter will be cached based on autotracking.\nIt will only rerun and create a new sorted array when the guests tracked\nproperty is updated.\n\n### Tradeoffs\n\nOveruse is discouraged.\n\nIn general, you should avoid using `@cached` unless you have confirmed that\nthe getter you are decorating is computationally expensive. `@cached` adds\na small amount of overhead to the getter, making it more expensive.\nWhile this overhead is small, if `@cached` is overused it can add up to a\nlarge impact overall in your app. Many getters and tracked properties\nare only accessed once, rendered, and then never rerendered, so adding\n`@cached` when it is unnecessary can negatively impact performance.\n\nAlso, `@cached` may rerun even if the values themselves have not changed,\nsince tracked properties will always invalidate even if their underlying\nvalue did not change.\nFor example updating an integer value from `5` to an other `5`.\n\nAvoiding a cache invalidation in this case is not something that can\nbe achieved on the `@cached` decorator itself, but rather when updating\nthe underlying values, by applying a diff checking mecanism:\n\n```javascript\nif (newValue !== this.trackedProp) {\n  this.trackedProp = newValue;\n}\n```\n\nHere equal values won't update the property, therefore not triggering a\ncache invalidation.\n\nThe cost of these edge-guards adds up to the tradoff calculation of using\na caching strategy, hence requiring a very sensitive approach regarding\nperformance.",
+      "itemtype": "method",
+      "name": "cached",
+      "static": 1,
+      "access": "public",
+      "tagname": "",
+      "class": "@glimmer/tracking",
+      "module": "@glimmer/tracking"
+    },
     {
       "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
-      "line": 91,
+      "line": 93,
       "description": "Override this function when writing a class-based helper.",
       "itemtype": "method",
       "name": "compute",
@@ -6423,7 +6428,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
-      "line": 115,
+      "line": 117,
       "description": "On a class-based helper, it may be useful to force a recomputation of that\nhelpers value. This is akin to `rerender` on a component.\n\nFor example, this component will rerender when the `currentUser` on a\nsession service changes:\n\n```app/helpers/current-user-email.js\nimport Helper from '@ember/component/helper'\nimport { service } from '@ember/service'\nimport { observer } from '@ember/object'\n\nexport default Helper.extend({\n  session: service(),\n\n  onNewUser: observer('session.currentUser', function() {\n    this.recompute();\n  }),\n\n  compute() {\n    return this.get('session.currentUser.email');\n  }\n});\n```",
       "itemtype": "method",
       "name": "recompute",
@@ -6435,7 +6440,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
-      "line": 267,
+      "line": 269,
       "description": "In many cases it is not necessary to use the full `Helper` class.\nThe `helper` method create pure-function helpers without instances.\nFor example:\n\n```app/helpers/format-currency.js\nimport { helper } from '@ember/component/helper';\n\nexport default helper(function([cents], {currency}) {\n  return `${currency}${cents * 0.01}`;\n});\n```",
       "static": 1,
       "params": [
@@ -6851,7 +6856,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/computed.ts",
-      "line": 604,
+      "line": 607,
       "description": "Call on a computed property to set it into read-only mode. When in this\nmode the computed property will throw an error when set.\n\nExample:\n\n```javascript\nimport { computed, set } from '@ember/object';\n\nclass Person {\n  @computed().readOnly()\n  get guid() {\n    return 'guid-guid-guid';\n  }\n}\n\nlet person = new Person();\nset(person, 'guid', 'new-guid'); // will throw an exception\n```\n\nClassic Class Example:\n\n```javascript\nimport EmberObject, { computed } from '@ember/object';\n\nlet Person = EmberObject.extend({\n  guid: computed(function() {\n    return 'guid-guid-guid';\n  }).readOnly()\n});\n\nlet person = Person.create();\nperson.set('guid', 'new-guid'); // will throw an exception\n```",
       "itemtype": "method",
       "name": "readOnly",
@@ -6867,7 +6872,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/computed.ts",
-      "line": 654,
+      "line": 657,
       "description": "In some cases, you may want to annotate computed properties with additional\nmetadata about how they function or what values they operate on. For example,\ncomputed property functions may close over variables that are then no longer\navailable for introspection. You can pass a hash of these values to a\ncomputed property.\n\nExample:\n\n```javascript\nimport { computed } from '@ember/object';\nimport Person from 'my-app/utils/person';\n\nclass Store {\n  @computed().meta({ type: Person })\n  get person() {\n    let personId = this.personId;\n    return Person.create({ id: personId });\n  }\n}\n```\n\nClassic Class Example:\n\n```javascript\nimport { computed } from '@ember/object';\nimport Person from 'my-app/utils/person';\n\nconst Store = EmberObject.extend({\n  person: computed(function() {\n    let personId = this.get('personId');\n    return Person.create({ id: personId });\n  }).meta({ type: Person })\n});\n```\n\nThe hash that you pass to the `meta()` function will be saved on the\ncomputed property descriptor under the `_meta` key. Ember runtime\nexposes a public API for retrieving these values from classes,\nvia the `metaForProperty()` function.",
       "itemtype": "method",
       "name": "meta",
@@ -6886,19 +6891,19 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/computed.ts",
-      "line": 713,
+      "line": 716,
       "class": "ComputedProperty",
       "module": "@ember/object"
     },
     {
       "file": "packages/@ember/-internals/metal/lib/computed.ts",
-      "line": 719,
+      "line": 722,
       "class": "ComputedProperty",
       "module": "@ember/object"
     },
     {
       "file": "packages/@ember/-internals/metal/lib/computed.ts",
-      "line": 727,
+      "line": 730,
       "description": "This helper returns a new property descriptor that wraps the passed\ncomputed property function. You can use this helper to define properties with\nnative decorator syntax, mixins, or via `defineProperty()`.\n\nExample:\n\n```js\nimport { computed, set } from '@ember/object';\n\nclass Person {\n  constructor() {\n    this.firstName = 'Betty';\n    this.lastName = 'Jones';\n  },\n\n  @computed('firstName', 'lastName')\n  get fullName() {\n    return `${this.firstName} ${this.lastName}`;\n  }\n}\n\nlet client = new Person();\n\nclient.fullName; // 'Betty Jones'\n\nset(client, 'lastName', 'Fuller');\nclient.fullName; // 'Betty Fuller'\n```\n\nClassic Class Example:\n\n```js\nimport EmberObject, { computed } from '@ember/object';\n\nlet Person = EmberObject.extend({\n  init() {\n    this._super(...arguments);\n\n    this.firstName = 'Betty';\n    this.lastName = 'Jones';\n  },\n\n  fullName: computed('firstName', 'lastName', function() {\n    return `${this.get('firstName')} ${this.get('lastName')}`;\n  })\n});\n\nlet client = Person.create();\n\nclient.get('fullName'); // 'Betty Jones'\n\nclient.set('lastName', 'Fuller');\nclient.get('fullName'); // 'Betty Fuller'\n```\n\nYou can also provide a setter, either directly on the class using native class\nsyntax, or by passing a hash with `get` and `set` functions.\n\nExample:\n\n```js\nimport { computed, set } from '@ember/object';\n\nclass Person {\n  constructor() {\n    this.firstName = 'Betty';\n    this.lastName = 'Jones';\n  },\n\n  @computed('firstName', 'lastName')\n  get fullName() {\n    return `${this.firstName} ${this.lastName}`;\n  }\n\n  set fullName(value) {\n    let [firstName, lastName] = value.split(/\\s+/);\n\n    set(this, 'firstName', firstName);\n    set(this, 'lastName', lastName);\n\n    return value;\n  }\n}\n\nlet client = new Person();\n\nclient.fullName; // 'Betty Jones'\n\nset(client, 'lastName', 'Fuller');\nclient.fullName; // 'Betty Fuller'\n```\n\nClassic Class Example:\n\n```js\nimport EmberObject, { computed } from '@ember/object';\n\nlet Person = EmberObject.extend({\n  init() {\n    this._super(...arguments);\n\n    this.firstName = 'Betty';\n    this.lastName = 'Jones';\n  },\n\n  fullName: computed('firstName', 'lastName', {\n    get(key) {\n      return `${this.get('firstName')} ${this.get('lastName')}`;\n    },\n    set(key, value) {\n      let [firstName, lastName] = value.split(/\\s+/);\n      this.setProperties({ firstName, lastName });\n      return value;\n    }\n  })\n});\n\nlet client = Person.create();\nclient.get('firstName'); // 'Betty'\n\nclient.set('fullName', 'Carroll Fuller');\nclient.get('firstName'); // 'Carroll'\n```\n\nWhen passed as an argument, the `set` function should accept two parameters,\n`key` and `value`. The value returned from `set` will be the new value of the\nproperty.\n\n_Note: This is the preferred way to define computed properties when writing third-party\nlibraries that depend on or use Ember, since there is no guarantee that the user\nwill have [prototype Extensions](https://guides.emberjs.com/release/configuring-ember/disabling-prototype-extensions/) enabled._",
       "itemtype": "method",
       "name": "computed",
@@ -6927,7 +6932,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/computed.ts",
-      "line": 915,
+      "line": 918,
       "description": "Allows checking if a given property on an object is a computed property. For the most part,\nthis doesn't matter (you would normally just access the property directly and use its value),\nbut for some tooling specific scenarios (e.g. the ember-inspector) it is important to\ndifferentiate if a property is a computed property or a \"normal\" property.\n\nThis will work on either a class's prototype or an instance itself.",
       "static": 1,
       "itemtype": "method",
@@ -6939,7 +6944,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/decorator.ts",
-      "line": 156,
+      "line": 157,
       "description": "Returns the CP descriptor associated with `obj` and `keyName`, if any.",
       "itemtype": "method",
       "name": "descriptorForProperty",
@@ -6966,7 +6971,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/decorator.ts",
-      "line": 184,
+      "line": 185,
       "description": "Check whether a value is a decorator",
       "itemtype": "method",
       "name": "isClassicDecorator",
@@ -6988,7 +6993,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/decorator.ts",
-      "line": 196,
+      "line": 197,
       "description": "Set a value as a decorator",
       "itemtype": "method",
       "name": "setClassicDecorator",
@@ -7035,7 +7040,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/events.ts",
-      "line": 27,
+      "line": 28,
       "description": "Add an event listener",
       "itemtype": "method",
       "name": "addListener",
@@ -7073,7 +7078,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/events.ts",
-      "line": 61,
+      "line": 62,
       "description": "Remove an event listener\n\nArguments should match those passed to `addListener`.",
       "itemtype": "method",
       "name": "removeListener",
@@ -7106,7 +7111,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/events.ts",
-      "line": 104,
+      "line": 105,
       "description": "Send an event. The execution of suspended listeners\nis skipped, and once listeners are removed. A listener without\na target is executed on the passed object. If an array of actions\nis not passed, the actions stored on the passed object are invoked.",
       "itemtype": "method",
       "name": "sendEvent",
@@ -7138,7 +7143,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/events.ts",
-      "line": 161,
+      "line": 162,
       "access": "public",
       "tagname": "",
       "itemtype": "method",
@@ -7164,7 +7169,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/events.ts",
-      "line": 179,
+      "line": 180,
       "description": "Define a property as a function that should be executed when\na specified event or events are triggered.\n\n``` javascript\nimport EmberObject from '@ember/object';\nimport { on } from '@ember/object/evented';\nimport { sendEvent } from '@ember/object/events';\n\nlet Job = EmberObject.extend({\n  logCompleted: on('completed', function() {\n    console.log('Job completed!');\n  })\n});\n\nlet job = Job.create();\n\nsendEvent(job, 'completed'); // Logs 'Job completed!'\n ```",
       "itemtype": "method",
       "name": "on",
@@ -7339,7 +7344,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 431,
+      "line": 428,
       "itemtype": "method",
       "name": "mixin",
       "params": [
@@ -7363,43 +7368,43 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 528,
+      "line": 525,
       "class": "Mixin",
       "module": "@ember/object"
     },
     {
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 531,
+      "line": 528,
       "class": "Mixin",
       "module": "@ember/object"
     },
     {
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 534,
+      "line": 531,
       "class": "Mixin",
       "module": "@ember/object"
     },
     {
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 537,
+      "line": 534,
       "class": "Mixin",
       "module": "@ember/object"
     },
     {
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 540,
+      "line": 537,
       "class": "Mixin",
       "module": "@ember/object"
     },
     {
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 545,
+      "line": 542,
       "class": "Mixin",
       "module": "@ember/object"
     },
     {
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 571,
+      "line": 568,
       "itemtype": "method",
       "name": "create",
       "static": 1,
@@ -7417,13 +7422,13 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 586,
+      "line": 583,
       "class": "@ember/object/mixin",
       "module": "@ember/object"
     },
     {
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 604,
+      "line": 601,
       "itemtype": "method",
       "name": "reopen",
       "params": [
@@ -7441,7 +7446,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 627,
+      "line": 624,
       "itemtype": "method",
       "name": "apply",
       "params": [
@@ -7461,13 +7466,13 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 643,
+      "line": 640,
       "class": "@ember/object/mixin",
       "module": "@ember/object"
     },
     {
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 648,
+      "line": 645,
       "itemtype": "method",
       "name": "detect",
       "params": [
@@ -7488,25 +7493,25 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 669,
+      "line": 666,
       "class": "@ember/object/mixin",
       "module": "@ember/object"
     },
     {
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 676,
+      "line": 673,
       "class": "@ember/object/mixin",
       "module": "@ember/object"
     },
     {
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 681,
+      "line": 678,
       "class": "@ember/object/mixin",
       "module": "@ember/object"
     },
     {
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 773,
+      "line": 770,
       "description": "Specify a method that observes property changes.\n\n```javascript\nimport EmberObject from '@ember/object';\nimport { observer } from '@ember/object';\n\nexport default EmberObject.extend({\n  valueObserver: observer('value', function() {\n    // Executes whenever the \"value\" property changes\n  })\n});\n```\n\nAlso available as `Function.prototype.observes` if prototype extensions are\nenabled.",
       "itemtype": "method",
       "name": "observer",
@@ -7534,7 +7539,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/observer.ts",
-      "line": 26,
+      "line": 27,
       "itemtype": "method",
       "name": "addObserver",
       "static": 1,
@@ -7567,7 +7572,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/observer.ts",
-      "line": 54,
+      "line": 55,
       "itemtype": "method",
       "name": "removeObserver",
       "static": 1,
@@ -7600,7 +7605,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/observer.ts",
-      "line": 154,
+      "line": 155,
       "description": "Primarily used for cases where we are redefining a class, e.g. mixins/reopen\nbeing applied later. Revalidates all the observers, resetting their tags.",
       "access": "private",
       "tagname": "",
@@ -7615,7 +7620,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/properties.ts",
-      "line": 11,
+      "line": 13,
       "description": "NOTE: This is a low-level method used by other parts of the API. You almost\nnever want to call this method directly. Instead you should use\n`mixin()` to define new properties.\n\nDefines a property on an object. This method works much like the ES5\n`Object.defineProperty()` method except that it can also accept computed\nproperties and other special descriptors.\n\nNormally this method takes only three parameters. However if you pass an\ninstance of `Descriptor` as the third param then you can pass an\noptional value as the fourth parameter. This is often more efficient than\ncreating new descriptor hashes for each property.\n\n## Examples\n\n```javascript\nimport { defineProperty, computed } from '@ember/object';\n\n// ES5 compatible mode\ndefineProperty(contact, 'firstName', {\n  writable: true,\n  configurable: false,\n  enumerable: true,\n  value: 'Charles'\n});\n\n// define a simple property\ndefineProperty(contact, 'lastName', undefined, 'Jolley');\n\n// define a computed property\ndefineProperty(contact, 'fullName', computed('firstName', 'lastName', function() {\n  return this.firstName+' '+this.lastName;\n}));\n```",
       "access": "public",
       "tagname": "",
@@ -7651,7 +7656,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/property_events.ts",
-      "line": 31,
+      "line": 32,
       "description": "This function is called just after an object property has changed.\nIt will notify any observers and clear caches among other things.\n\nNormally you will not need to call this method directly but if for some\nreason you can't directly watch a property you can invoke this method\nmanually.",
       "itemtype": "method",
       "name": "notifyPropertyChange",
@@ -7691,7 +7696,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/property_events.ts",
-      "line": 82,
+      "line": 83,
       "itemtype": "method",
       "name": "beginPropertyChanges",
       "chainable": 1,
@@ -7702,7 +7707,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/property_events.ts",
-      "line": 92,
+      "line": 93,
       "itemtype": "method",
       "name": "endPropertyChanges",
       "access": "private",
@@ -7712,7 +7717,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/property_events.ts",
-      "line": 104,
+      "line": 105,
       "description": "Make a series of property changes together in an\nexception-safe way.\n\n```javascript\nEmber.changeProperties(function() {\n  obj1.set('foo', mayBlowUpWhenSet);\n  obj2.set('bar', baz);\n});\n```",
       "itemtype": "method",
       "name": "changeProperties",
@@ -7846,7 +7851,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/tracked.ts",
-      "line": 17,
+      "line": 12,
       "decorator": "",
       "access": "private",
       "tagname": "Marks a property as tracked.\n\nBy default, a component's properties are expected to be static,\nmeaning you are not able to update them and have the template update accordingly.\nMarking a property as tracked means that when that property changes,\na rerender of the component is scheduled so the template is kept up to date.\n\nThere are two usages for the `@tracked` decorator, shown below.",
@@ -7914,7 +7919,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/ext/controller.ts",
-      "line": 25,
+      "line": 26,
       "description": "Defines which query parameters the controller accepts.\nIf you give the names `['category','page']` it will bind\nthe values of these query parameters to the variables\n`this.category` and `this.page`.\n\nBy default, query parameters are parsed as strings. This\nmay cause unexpected behavior if a query parameter is used with `toggleProperty`,\nbecause the initial value set for `param=false` will be the string `\"false\"`, which is truthy.\n\nTo avoid this, you may specify that the query parameter should be parsed as a boolean\nby using the following verbose form with a `type` property:\n```javascript\n  queryParams: [{\n    category: {\n      type: 'boolean'\n    }\n  }]\n```\nAvailable values for the `type` parameter are `'boolean'`, `'number'`, `'array'`, and `'string'`.\nIf query param type is not specified, it will default to `'string'`.",
       "itemtype": "property",
       "name": "queryParams",
@@ -7925,7 +7930,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/ext/controller.ts",
-      "line": 53,
+      "line": 54,
       "description": "This property is updated to various different callback functions depending on\nthe current \"state\" of the backing route. It is used by\n`Controller.prototype._qpChanged`.\n\nThe methods backing each state can be found in the `Route.prototype._qp` computed\nproperty return value (the `.states` property). The current values are listed here for\nthe sanity of future travelers:\n\n* `inactive` - This state is used when this controller instance is not part of the active\n  route hierarchy. Set in `Route.prototype._reset` (a `router.js` microlib hook) and\n  `Route.prototype.actions.finalizeQueryParamChange`.\n* `active` - This state is used when this controller instance is part of the active\n  route hierarchy. Set in `Route.prototype.actions.finalizeQueryParamChange`.\n* `allowOverrides` - This state is used in `Route.prototype.setup` (`route.js` microlib hook).",
       "itemtype": "method",
       "name": "_qpDelegate",
@@ -7936,7 +7941,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/ext/controller.ts",
-      "line": 74,
+      "line": 75,
       "description": "During `Route#setup` observers are created to invoke this method\nwhen any of the query params declared in `Controller#queryParams` property\nare changed.\n\nWhen invoked this method uses the currently active query param update delegate\n(see `Controller.prototype._qpDelegate` for details) and invokes it with\nthe QP key/value being changed.",
       "itemtype": "method",
       "name": "_qpChanged",
@@ -7947,7 +7952,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/ext/controller.ts",
-      "line": 95,
+      "line": 96,
       "description": "Transition the application into another route. The route may\nbe either a single route or route path:\n\n```javascript\naController.transitionToRoute('blogPosts');\naController.transitionToRoute('blogPosts.recentEntries');\n```\n\nOptionally supply a model for the route in question. The model\nwill be serialized into the URL using the `serialize` hook of\nthe route:\n\n```javascript\naController.transitionToRoute('blogPost', aPost);\n```\n\nIf a literal is passed (such as a number or a string), it will\nbe treated as an identifier instead. In this case, the `model`\nhook of the route will be triggered:\n\n```javascript\naController.transitionToRoute('blogPost', 1);\n```\n\nMultiple models will be applied last to first recursively up the\nroute tree.\n\n```app/router.js\nRouter.map(function() {\n  this.route('blogPost', { path: ':blogPostId' }, function() {\n    this.route('blogComment', { path: ':blogCommentId', resetNamespace: true });\n  });\n});\n```\n\n```javascript\naController.transitionToRoute('blogComment', aPost, aComment);\naController.transitionToRoute('blogComment', 1, 13);\n```\n\nIt is also possible to pass a URL (a string that starts with a\n`/`).\n\n```javascript\naController.transitionToRoute('/');\naController.transitionToRoute('/blog/post/1/comment/13');\naController.transitionToRoute('/blog/posts?sort=title');\n```\n\nAn options hash with a `queryParams` property may be provided as\nthe final argument to add query parameters to the destination URL.\n\n```javascript\naController.transitionToRoute('blogPost', 1, {\n  queryParams: { showComments: 'true' }\n});\n\n// if you just want to transition the query parameters without changing the route\naController.transitionToRoute({ queryParams: { sort: 'date' } });\n```\n\nSee also [replaceRoute](/ember/release/classes/Ember.ControllerMixin/methods/replaceRoute?anchor=replaceRoute).",
       "itemtype": "method",
       "name": "transitionToRoute",
@@ -7983,7 +7988,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/ext/controller.ts",
-      "line": 185,
+      "line": 186,
       "description": "Transition into another route while replacing the current URL, if possible.\nThis will replace the current history entry instead of adding a new one.\nBeside that, it is identical to `transitionToRoute` in all other respects.\n\n```javascript\naController.replaceRoute('blogPosts');\naController.replaceRoute('blogPosts.recentEntries');\n```\n\nOptionally supply a model for the route in question. The model\nwill be serialized into the URL using the `serialize` hook of\nthe route:\n\n```javascript\naController.replaceRoute('blogPost', aPost);\n```\n\nIf a literal is passed (such as a number or a string), it will\nbe treated as an identifier instead. In this case, the `model`\nhook of the route will be triggered:\n\n```javascript\naController.replaceRoute('blogPost', 1);\n```\n\nMultiple models will be applied last to first recursively up the\nroute tree.\n\n```app/router.js\nRouter.map(function() {\n  this.route('blogPost', { path: ':blogPostId' }, function() {\n    this.route('blogComment', { path: ':blogCommentId', resetNamespace: true });\n  });\n});\n```\n\n```\naController.replaceRoute('blogComment', aPost, aComment);\naController.replaceRoute('blogComment', 1, 13);\n```\n\nIt is also possible to pass a URL (a string that starts with a\n`/`).\n\n```javascript\naController.replaceRoute('/');\naController.replaceRoute('/blog/post/1/comment/13');\n```",
       "itemtype": "method",
       "name": "replaceRoute",
@@ -8559,7 +8564,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 81,
+      "line": 82,
       "description": "Transition the application into another route. The route may\nbe either a single route or route path:\n\nCalling `transitionTo` from the Router service will cause default query parameter values to be included in the URL.\nThis behavior is different from calling `transitionTo` on a route or `transitionToRoute` on a controller.\nSee the [Router Service RFC](https://github.com/emberjs/rfcs/blob/master/text/0095-router-service.md#query-parameter-semantics) for more info.\n\nIn the following example we use the Router service to navigate to a route with a\nspecific model from a Component in the first action, and in the second we trigger\na query-params only transition.\n\n```app/components/example.js\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\nimport { service } from '@ember/service';\n\nexport default class extends Component {\n  @service router;\n\n  @action\n  goToComments(post) {\n    this.router.transitionTo('comments', post);\n  }\n\n  @action\n  fetchMoreComments(latestComment) {\n    this.router.transitionTo({\n      queryParams: { commentsAfter: latestComment }\n    });\n  }\n}\n```",
       "itemtype": "method",
       "name": "transitionTo",
@@ -8594,7 +8599,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 140,
+      "line": 141,
       "description": "Similar to `transitionTo`, but instead of adding the destination to the browser's URL history,\nit replaces the entry for the current route.\nWhen the user clicks the \"back\" button in the browser, there will be fewer steps.\nThis is most commonly used to manage redirects in a way that does not cause confusing additions\nto the user's browsing history.\n\nCalling `replaceWith` from the Router service will cause default query parameter values to be included in the URL.\nThis behavior is different from calling `replaceWith` on a route.\nSee the [Router Service RFC](https://github.com/emberjs/rfcs/blob/master/text/0095-router-service.md#query-parameter-semantics) for more info.\n\nUsage example:\n\n```app/routes/application.js\nimport Route from '@ember/routing/route';\n\nexport default class extends Route {\n  beforeModel() {\n    if (!authorized()){\n      this.replaceWith('unauthorized');\n    }\n  }\n});\n```",
       "itemtype": "method",
       "name": "replaceWith",
@@ -8627,7 +8632,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 179,
+      "line": 180,
       "description": "Generate a URL based on the supplied route name and optionally a model. The\nURL is returned as a string that can be used for any purpose.\n\nIn this example, the URL for the `author.books` route for a given author\nis copied to the clipboard.\n\n```app/templates/application.hbs\n<CopyLink @author={{hash id=\"tomster\" name=\"Tomster\"}} />\n```\n\n```app/components/copy-link.js\nimport Component from '@glimmer/component';\nimport { service } from '@ember/service';\nimport { action } from '@ember/object';\n\nexport default class CopyLinkComponent extends Component {\n  @service router;\n  @service clipboard;\n\n  @action\n  copyBooksURL() {\n    if (this.author) {\n      const url = this.router.urlFor('author.books', this.args.author);\n      this.clipboard.set(url);\n      // Clipboard now has /author/tomster/books\n    }\n  }\n}\n```\n\nJust like with `transitionTo` and `replaceWith`, `urlFor` can also handle\nquery parameters.\n\n```app/templates/application.hbs\n<CopyLink @author={{hash id=\"tomster\" name=\"Tomster\"}} />\n```\n\n```app/components/copy-link.js\nimport Component from '@glimmer/component';\nimport { service } from '@ember/service';\nimport { action } from '@ember/object';\n\nexport default class CopyLinkComponent extends Component {\n  @service router;\n  @service clipboard;\n\n  @action\n  copyOnlyEmberBooksURL() {\n    if (this.author) {\n      const url = this.router.urlFor('author.books', this.author, {\n        queryParams: { filter: 'emberjs' }\n      });\n      this.clipboard.set(url);\n      // Clipboard now has /author/tomster/books?filter=emberjs\n    }\n  }\n}\n```",
       "itemtype": "method",
       "name": "urlFor",
@@ -8660,7 +8665,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 252,
+      "line": 253,
       "description": "Returns `true` if `routeName/models/queryParams` is the active route, where `models` and `queryParams` are optional.\nSee [model](api/ember/release/classes/Route/methods/model?anchor=model) and\n[queryParams](/api/ember/3.7/classes/Route/properties/queryParams?anchor=queryParams) for more information about these arguments.\n\nIn the following example, `isActive` will return `true` if the current route is `/posts`.\n\n```app/components/posts.js\nimport Component from '@glimmer/component';\nimport { service } from '@ember/service';\n\nexport default class extends Component {\n  @service router;\n\n  displayComments() {\n    return this.router.isActive('posts');\n  }\n});\n```\n\nThe next example includes a dynamic segment, and will return `true` if the current route is `/posts/1`,\nassuming the post has an id of 1:\n\n```app/components/posts.js\nimport Component from '@glimmer/component';\nimport { service } from '@ember/service';\n\nexport default class extends Component {\n  @service router;\n\n  displayComments(post) {\n    return this.router.isActive('posts', post.id);\n  }\n});\n```\n\nWhere `post.id` is the id of a specific post, which is represented in the route as /posts/[post.id].\nIf `post.id` is equal to 1, then isActive will return true if the current route is /posts/1, and false if the route is anything else.",
       "itemtype": "method",
       "name": "isActive",
@@ -8693,7 +8698,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 356,
+      "line": 357,
       "description": "Takes a string URL and returns a `RouteInfo` for the leafmost route represented\nby the URL. Returns `null` if the URL is not recognized. This method expects to\nreceive the actual URL as seen by the browser including the app's `rootURL`.\n\nSee [RouteInfo](/ember/release/classes/RouteInfo) for more info.\n\nIn the following example `recognize` is used to verify if a path belongs to our\napplication before transitioning to it.\n\n```\nimport Component from '@ember/component';\nimport { service } from '@ember/service';\n\nexport default class extends Component {\n  @service router;\n  path = '/';\n\n  click() {\n    if (this.router.recognize(this.path)) {\n      this.router.transitionTo(this.path);\n    }\n  }\n}\n```",
       "itemtype": "method",
       "name": "recognize",
@@ -8715,7 +8720,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 397,
+      "line": 398,
       "description": "Takes a string URL and returns a promise that resolves to a\n`RouteInfoWithAttributes` for the leafmost route represented by the URL.\nThe promise rejects if the URL is not recognized or an unhandled exception\nis encountered. This method expects to receive the actual URL as seen by\nthe browser including the app's `rootURL`.",
       "itemtype": "method",
       "name": "recognizeAndLoad",
@@ -8737,7 +8742,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 419,
+      "line": 420,
       "description": "You can register a listener for events emitted by this service with `.on()`:\n\n```app/routes/contact-form.js\nimport Route from '@ember/routing';\nimport { service } from '@ember/service';\n\nexport default class extends Route {\n  @service router;\n\n  activate() {\n    this.router.on('routeWillChange', (transition) => {\n      if (!transition.to.find(route => route.name === this.routeName)) {\n        alert(\"Please save or cancel your changes.\");\n        transition.abort();\n      }\n    })\n  }\n}\n```",
       "itemtype": "method",
       "name": "on",
@@ -8760,7 +8765,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 446,
+      "line": 447,
       "description": "You can unregister a listener for events emitted by this service with `.off()`:\n\n```app/routes/contact-form.js\nimport Route from '@ember/routing';\nimport { service } from '@ember/service';\n\nexport default class extends Route {\n  @service router;\n\n  callback = (transition) =>  {\n    if (!transition.to.find(route => route.name === this.routeName)) {\n      alert(\"Please save or cancel your changes.\");\n      transition.abort();\n    }\n  };\n\n  activate() {\n    this.router.on('routeWillChange', this.callback);\n  }\n\n  deactivate() {\n    this.router.off('routeWillChange', this.callback);\n}\n```",
       "itemtype": "method",
       "name": "off",
@@ -8783,7 +8788,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 478,
+      "line": 479,
       "description": "The `routeWillChange` event is fired at the beginning of any\nattempted transition with a `Transition` object as the sole\nargument. This action can be used for aborting, redirecting,\nor decorating the transition from the currently active routes.\n\nA good example is preventing navigation when a form is\nhalf-filled out:\n\n```app/routes/contact-form.js\nimport Route from '@ember/routing';\nimport { service } from '@ember/service';\n\nexport default class extends Route {\n  @service router;\n\n  activate() {\n    this.router.on('routeWillChange', (transition) => {\n      if (!transition.to.find(route => route.name === this.routeName)) {\n        alert(\"Please save or cancel your changes.\");\n        transition.abort();\n      }\n    })\n  }\n}\n```\n\nThe `routeWillChange` event fires whenever a new route is chosen as the desired target of a transition. This includes `transitionTo`, `replaceWith`, all redirection for any reason including error handling, and abort. Aborting implies changing the desired target back to where you already were. Once a transition has completed, `routeDidChange` fires.",
       "itemtype": "event",
       "name": "routeWillChange",
@@ -8801,7 +8806,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 512,
+      "line": 513,
       "description": "The `routeDidChange` event only fires once a transition has settled.\nThis includes aborts and error substates. Like the `routeWillChange` event\nit receives a Transition as the sole argument.\n\nA good example is sending some analytics when the route has transitioned:\n\n```app/routes/contact-form.js\nimport Route from '@ember/routing';\nimport { service } from '@ember/service';\n\nexport default class extends Route {\n  @service router;\n\n  activate() {\n    this.router.on('routeDidChange', (transition) => {\n      ga.send('pageView', {\n        current: transition.to.name,\n        from: transition.from.name\n      });\n    })\n  }\n}\n```\n\n`routeDidChange` will be called after any `Route`'s\n[didTransition](/ember/release/classes/Route/events/didTransition?anchor=didTransition)\naction has been fired.\nThe updates of properties\n[currentURL](/ember/release/classes/RouterService/properties/currentURL?anchor=currentURL),\n[currentRouteName](/ember/release/classes/RouterService/properties/currentURL?anchor=currentRouteName)\nand\n[currentRoute](/ember/release/classes/RouterService/properties/currentURL?anchor=currentRoute)\nare completed at the time `routeDidChange` is called.",
       "itemtype": "event",
       "name": "routeDidChange",
@@ -8819,7 +8824,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 552,
+      "line": 553,
       "description": "Refreshes all currently active routes, doing a full transition.\nIf a route name is provided and refers to a currently active route,\nit will refresh only that route and its descendents.\nReturns a promise that will be resolved once the refresh is complete.\nAll resetController, beforeModel, model, afterModel, redirect, and setupController\nhooks will be called again. You will get new data from the model hook.",
       "itemtype": "method",
       "name": "refresh",
@@ -8841,7 +8846,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 582,
+      "line": 583,
       "description": "Name of the current route.\n\n This property represents the logical name of the route,\n which is dot separated.\n For the following router:\n\n ```app/router.js\n Router.map(function() {\n   this.route('about');\n   this.route('blog', function () {\n     this.route('post', { path: ':post_id' });\n   });\n });\n ```\n\n It will return:\n\n * `index` when you visit `/`\n * `about` when you visit `/about`\n * `blog.index` when you visit `/blog`\n * `blog.post` when you visit `/blog/some-post-id`",
       "itemtype": "property",
       "name": "currentRouteName",
@@ -8853,7 +8858,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 612,
+      "line": 613,
       "description": "Current URL for the application.\n\n  This property represents the URL path for this route.\n  For the following router:\n\n ```app/router.js\n Router.map(function() {\n   this.route('about');\n   this.route('blog', function () {\n     this.route('post', { path: ':post_id' });\n   });\n });\n ```\n\n It will return:\n\n * `/` when you visit `/`\n * `/about` when you visit `/about`\n * `/blog` when you visit `/blog`\n * `/blog/some-post-id` when you visit `/blog/some-post-id`",
       "itemtype": "property",
       "name": "currentURL",
@@ -8865,7 +8870,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 641,
+      "line": 642,
       "description": "The `location` property returns what implementation of the `location` API\nyour application is using, which determines what type of URL is being used.\n\nSee [Location](/ember/release/classes/Location) for more information.\n\nTo force a particular `location` API implementation to be used in your\napplication you can set a location type on your `config/environment`.\nFor example, to set the `history` type:\n\n```config/environment.js\n'use strict';\n\nmodule.exports = function(environment) {\n  let ENV = {\n    modulePrefix: 'router-service',\n    environment,\n    rootURL: '/',\n    locationType: 'history',\n    ...\n  }\n}\n```\n\nThe following location types are available by default:\n`auto`, `hash`, `history`, `none`.\n\nSee [HashLocation](/ember/release/classes/HashLocation).\nSee [HistoryLocation](/ember/release/classes/HistoryLocation).\nSee [NoneLocation](/ember/release/classes/NoneLocation).\nSee [AutoLocation](/ember/release/classes/AutoLocation).",
       "itemtype": "property",
       "name": "location",
@@ -8880,7 +8885,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 681,
+      "line": 682,
       "description": "The `rootURL` property represents the URL of the root of\nthe application, '/' by default.\nThis prefix is assumed on all routes defined on this app.\n\nIf you change the `rootURL` in your environment configuration\nlike so:\n\n```config/environment.js\n'use strict';\n\nmodule.exports = function(environment) {\n  let ENV = {\n    modulePrefix: 'router-service',\n    environment,\n    rootURL: '/my-root',\n  …\n  }\n]\n```\n\nThis property will return `/my-root`.",
       "itemtype": "property",
       "name": "rootURL",
@@ -8892,7 +8897,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 711,
+      "line": 712,
       "description": "The `currentRoute` property contains metadata about the current leaf route.\nIt returns a `RouteInfo` object that has information like the route name,\nparams, query params and more.\n\nSee [RouteInfo](/ember/release/classes/RouteInfo) for more info.\n\nThis property is guaranteed to change whenever a route transition\nhappens (even when that transition only changes parameters\nand doesn't change the active route).\n\nUsage example:\n```app/components/header.js\n  import Component from '@glimmer/component';\n  import { service } from '@ember/service';\n  import { notEmpty } from '@ember/object/computed';\n\n  export default class extends Component {\n    @service router;\n\n    @notEmpty('router.currentRoute.child') isChildRoute;\n  });\n```",
       "itemtype": "property",
       "name": "currentRoute",
@@ -9198,7 +9203,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 97,
+      "line": 96,
       "description": "The `willTransition` action is fired at the beginning of any\nattempted transition with a `Transition` object as the sole\nargument. This action can be used for aborting, redirecting,\nor decorating the transition from the currently active routes.\n\nA good example is preventing navigation when a form is\nhalf-filled out:\n\n```app/routes/contact-form.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class ContactFormRoute extends Route {\n  @action\n  willTransition(transition) {\n    if (this.controller.get('userHasEnteredData')) {\n      this.controller.displayNavigationConfirm();\n      transition.abort();\n    }\n  }\n}\n```\n\nYou can also redirect elsewhere by calling\n`this.transitionTo('elsewhere')` from within `willTransition`.\nNote that `willTransition` will not be fired for the\nredirecting `transitionTo`, since `willTransition` doesn't\nfire when there is already a transition underway. If you want\nsubsequent `willTransition` actions to fire for the redirecting\ntransition, you must first explicitly call\n`transition.abort()`.\n\nTo allow the `willTransition` event to continue bubbling to the parent\nroute, use `return true;`. When the `willTransition` method has a\nreturn value of `true` then the parent route's `willTransition` method\nwill be fired, enabling \"bubbling\" behavior for the event.",
       "itemtype": "event",
       "name": "willTransition",
@@ -9217,7 +9222,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 142,
+      "line": 141,
       "description": "The `didTransition` action is fired after a transition has\nsuccessfully been completed. This occurs after the normal model\nhooks (`beforeModel`, `model`, `afterModel`, `setupController`)\nhave resolved. The `didTransition` action has no arguments,\nhowever, it can be useful for tracking page views or resetting\nstate on the controller.\n\n```app/routes/login.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class LoginRoute extends Route {\n  @action\n  didTransition() {\n    this.controller.get('errors.base').clear();\n    return true; // Bubble the didTransition event\n  }\n}\n```",
       "itemtype": "event",
       "name": "didTransition",
@@ -9229,7 +9234,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 169,
+      "line": 168,
       "description": "The `loading` action is fired on the route when a route's `model`\nhook returns a promise that is not already resolved. The current\n`Transition` object is the first parameter and the route that\ntriggered the loading event is the second parameter.\n\n```app/routes/application.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class ApplicationRoute extends Route {\n  @action\n  loading(transition, route) {\n    let controller = this.controllerFor('foo');\n\n    // The controller may not be instantiated when initially loading\n    if (controller) {\n      controller.currentlyLoading = true;\n\n      transition.finally(function() {\n        controller.currentlyLoading = false;\n      });\n    }\n  }\n}\n```",
       "itemtype": "event",
       "name": "loading",
@@ -9253,7 +9258,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 204,
+      "line": 203,
       "description": "When attempting to transition into a route, any of the hooks\nmay return a promise that rejects, at which point an `error`\naction will be fired on the partially-entered routes, allowing\nfor per-route error handling logic, or shared error handling\nlogic defined on a parent route.\n\nHere is an example of an error handler that will be invoked\nfor rejected promises from the various hooks on the route,\nas well as any unhandled errors from child routes:\n\n```app/routes/admin.js\nimport { reject } from 'rsvp';\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class AdminRoute extends Route {\n  beforeModel() {\n    return reject('bad things!');\n  }\n\n  @action\n  error(error, transition) {\n    // Assuming we got here due to the error in `beforeModel`,\n    // we can expect that error === \"bad things!\",\n    // but a promise model rejecting would also\n    // call this hook, as would any errors encountered\n    // in `afterModel`.\n\n    // The `error` hook is also provided the failed\n    // `transition`, which can be stored and later\n    // `.retry()`d if desired.\n\n    this.transitionTo('login');\n  }\n}\n```\n\n`error` actions that bubble up all the way to `ApplicationRoute`\nwill fire a default error handler that logs the error. You can\nspecify your own global default error handler by overriding the\n`error` handler on `ApplicationRoute`:\n\n```app/routes/application.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class ApplicationRoute extends Route {\n  @action\n  error(error, transition) {\n    this.controllerFor('banner').displayError(error.message);\n  }\n}\n```",
       "itemtype": "event",
       "name": "error",
@@ -9277,7 +9282,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 311,
+      "line": 310,
       "description": "A hook you can implement to convert the route's model into parameters\nfor the URL.\n\n```app/router.js\n// ...\n\nRouter.map(function() {\n  this.route('post', { path: '/posts/:post_id' });\n});\n\n```\n\n```app/routes/post.js\nimport Route from '@ember/routing/route';\n\nexport default class PostRoute extends Route {\n  model({ post_id }) {\n    // the server returns `{ id: 12 }`\n    return fetch(`/posts/${post_id}`;\n  }\n\n  serialize(model) {\n    // this will make the URL `/posts/12`\n    return { post_id: model.id };\n  }\n}\n```\n\nThe default `serialize` method will insert the model's `id` into the\nroute's dynamic segment (in this case, `:post_id`) if the segment contains '_id'.\nIf the route has multiple dynamic segments or does not contain '_id', `serialize`\nwill return `getProperties(model, params)`\n\nThis method is called when `transitionTo` is called with a context\nin order to populate the URL.",
       "itemtype": "method",
       "name": "serialize",
@@ -9305,7 +9310,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 379,
+      "line": 378,
       "description": "Configuration hash for this route's queryParams. The possible\nconfiguration options and their defaults are as follows\n(assuming a query param whose controller property is `page`):\n\n```javascript\nqueryParams = {\n  page: {\n    // By default, controller query param properties don't\n    // cause a full transition when they are changed, but\n    // rather only cause the URL to update. Setting\n    // `refreshModel` to true will cause an \"in-place\"\n    // transition to occur, whereby the model hooks for\n    // this route (and any child routes) will re-fire, allowing\n    // you to reload models (e.g., from the server) using the\n    // updated query param values.\n    refreshModel: false,\n\n    // By default, changes to controller query param properties\n    // cause the URL to update via `pushState`, which means an\n    // item will be added to the browser's history, allowing\n    // you to use the back button to restore the app to the\n    // previous state before the query param property was changed.\n    // Setting `replace` to true will use `replaceState` (or its\n    // hash location equivalent), which causes no browser history\n    // item to be added. This options name and default value are\n    // the same as the `link-to` helper's `replace` option.\n    replace: false,\n\n    // By default, the query param URL key is the same name as\n    // the controller property name. Use `as` to specify a\n    // different URL key.\n    as: 'page'\n  }\n};\n```",
       "itemtype": "property",
       "name": "queryParams",
@@ -9318,8 +9323,8 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 432,
-      "description": "The name of the template to use by default when rendering this routes\ntemplate.\n\n```app/routes/posts/list.js\nimport Route from '@ember/routing/route';\n\nexport default class extends Route {\n  templateName = 'posts/list'\n});\n```\n\n```app/routes/posts/index.js\nimport PostsList from '../posts/list';\n\nexport default class extends PostsList {};\n```\n\n```app/routes/posts/archived.js\nimport PostsList from '../posts/list';\n\nexport default class extends PostsList {};\n```",
+      "line": 431,
+      "description": "The name of the template to use by default when rendering this route's\ntemplate.\n\n```app/routes/posts/list.js\nimport Route from '@ember/routing/route';\n\nexport default class PostsListRoute extends Route {\n  templateName = 'posts/list';\n}\n```\n\n```app/routes/posts/index.js\nimport PostsListRoute from '../posts/list';\n\nexport default class PostsIndexRoute extends PostsListRoute {};\n```\n\n```app/routes/posts/archived.js\nimport PostsListRoute from '../posts/list';\n\nexport default class PostsArchivedRoute extends PostsListRoute {};\n```",
       "itemtype": "property",
       "name": "templateName",
       "type": "String",
@@ -9332,7 +9337,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 465,
+      "line": 464,
       "description": "The name of the controller to associate with this route.\n\nBy default, Ember will lookup a route's controller that matches the name\nof the route (i.e. `posts.new`). However,\nif you would like to define a specific controller to use, you can do so\nusing this property.\n\nThis is useful in many ways, as the controller specified will be:\n\n* passed to the `setupController` method.\n* used as the controller for the template being rendered by the route.\n* returned from a call to `controllerFor` for the route.",
       "itemtype": "property",
       "name": "controllerName",
@@ -9346,7 +9351,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 488,
+      "line": 487,
       "description": "The controller associated with this route.\n\nExample\n\n```app/routes/form.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class FormRoute extends Route {\n  @action\n  willTransition(transition) {\n    if (this.controller.get('userHasEnteredData') &&\n        !confirm('Are you sure you want to abandon progress?')) {\n      transition.abort();\n    } else {\n      // Bubble the `willTransition` action so that\n      // parent routes can decide whether or not to abort.\n      return true;\n    }\n  }\n}\n```",
       "itemtype": "property",
       "name": "controller",
@@ -9359,7 +9364,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 519,
+      "line": 518,
       "description": "The name of the route, dot-delimited.\n\nFor example, a route found at `app/routes/posts/post.js` will have\na `routeName` of `posts.post`.",
       "itemtype": "property",
       "name": "routeName",
@@ -9372,7 +9377,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 533,
+      "line": 532,
       "description": "The name of the route, dot-delimited, including the engine prefix\nif applicable.\n\nFor example, a route found at `addon/routes/posts/post.js` within an\nengine named `admin` will have a `fullRouteName` of `admin.posts.post`.",
       "itemtype": "property",
       "name": "fullRouteName",
@@ -9385,7 +9390,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 548,
+      "line": 547,
       "description": "Sets the name for this route, including a fully resolved name for routes\ninside engines.",
       "access": "private",
       "tagname": "",
@@ -9403,7 +9408,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 563,
+      "line": 562,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -9413,7 +9418,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 597,
+      "line": 596,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -9423,7 +9428,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 606,
+      "line": 605,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -9433,7 +9438,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 614,
+      "line": 613,
       "description": "Returns a hash containing the parameters of an ancestor route.\n\nYou may notice that `this.paramsFor` sometimes works when referring to a\nchild route, but this behavior should not be relied upon as only ancestor\nroutes are certain to be loaded in time.\n\nExample\n\n```app/router.js\n// ...\n\nRouter.map(function() {\n  this.route('member', { path: ':name' }, function() {\n    this.route('interest', { path: ':interest' });\n  });\n});\n```\n\n```app/routes/member.js\nimport Route from '@ember/routing/route';\n\nexport default class MemberRoute extends Route {\n  queryParams = {\n    memberQp: { refreshModel: true }\n  }\n}\n```\n\n```app/routes/member/interest.js\nimport Route from '@ember/routing/route';\n\nexport default class MemberInterestRoute extends Route {\n  queryParams = {\n    interestQp: { refreshModel: true }\n  }\n\n  model() {\n    return this.paramsFor('member');\n  }\n}\n```\n\nIf we visit `/turing/maths?memberQp=member&interestQp=interest` the model for\nthe `member.interest` route is a hash with:\n\n* `name`: `turing`\n* `memberQp`: `member`",
       "itemtype": "method",
       "name": "paramsFor",
@@ -9456,7 +9461,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 695,
+      "line": 694,
       "description": "Serializes the query parameter key",
       "itemtype": "method",
       "name": "serializeQueryParamKey",
@@ -9474,7 +9479,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 706,
+      "line": 705,
       "description": "Serializes value of the query parameter based on defaultValueType",
       "itemtype": "method",
       "name": "serializeQueryParam",
@@ -9502,7 +9507,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 722,
+      "line": 721,
       "description": "Deserializes value of the query parameter based on defaultValueType",
       "itemtype": "method",
       "name": "deserializeQueryParam",
@@ -9530,7 +9535,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 738,
+      "line": 737,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -9540,7 +9545,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 754,
+      "line": 753,
       "description": "A hook you can use to reset controller values either when the model\nchanges or the route is exiting.\n\n```app/routes/articles.js\nimport Route from '@ember/routing/route';\n\nexport default class ArticlesRoute extends Route {\n  resetController(controller, isExiting, transition) {\n    if (isExiting && transition.targetName !== 'error') {\n      controller.set('page', 1);\n    }\n  }\n}\n```",
       "itemtype": "method",
       "name": "resetController",
@@ -9569,7 +9574,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 781,
+      "line": 780,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -9579,7 +9584,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 792,
+      "line": 791,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -9590,7 +9595,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 806,
+      "line": 805,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -9600,7 +9605,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 817,
+      "line": 816,
       "description": "This event is triggered when the router enters the route. It is\nnot executed when the model for the route changes.\n\n```app/routes/application.js\nimport { on } from '@ember/object/evented';\nimport Route from '@ember/routing/route';\n\nexport default Route.extend({\n  collectAnalytics: on('activate', function(){\n    collectAnalytics();\n  })\n});\n```",
       "itemtype": "event",
       "name": "activate",
@@ -9612,7 +9617,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 837,
+      "line": 836,
       "description": "This event is triggered when the router completely exits this\nroute. It is not executed when the model for the route changes.\n\n```app/routes/index.js\nimport { on } from '@ember/object/evented';\nimport Route from '@ember/routing/route';\n\nexport default Route.extend({\n  trackPageLeaveAnalytics: on('deactivate', function(){\n    trackPageLeaveAnalytics();\n  })\n});\n```",
       "itemtype": "event",
       "name": "deactivate",
@@ -9624,7 +9629,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 857,
+      "line": 856,
       "description": "This hook is executed when the router completely exits this route. It is\nnot executed when the model for the route changes.",
       "itemtype": "method",
       "name": "deactivate",
@@ -9643,7 +9648,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 868,
+      "line": 867,
       "description": "This hook is executed when the router enters the route. It is not executed\nwhen the model for the route changes.",
       "itemtype": "method",
       "name": "activate",
@@ -9662,7 +9667,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 879,
+      "line": 878,
       "description": "Transition the application into another route. The route may\nbe either a single route or route path:\n\n```javascript\nthis.transitionTo('blogPosts');\nthis.transitionTo('blogPosts.recentEntries');\n```\n\nOptionally supply a model for the route in question. The model\nwill be serialized into the URL using the `serialize` hook of\nthe route:\n\n```javascript\nthis.transitionTo('blogPost', aPost);\n```\n\nIf a literal is passed (such as a number or a string), it will\nbe treated as an identifier instead. In this case, the `model`\nhook of the route will be triggered:\n\n```javascript\nthis.transitionTo('blogPost', 1);\n```\n\nMultiple models will be applied last to first recursively up the\nroute tree.\n\n```app/routes.js\n// ...\n\nRouter.map(function() {\n  this.route('blogPost', { path:':blogPostId' }, function() {\n    this.route('blogComment', { path: ':blogCommentId' });\n  });\n});\n\nexport default Router;\n```\n\n```javascript\nthis.transitionTo('blogComment', aPost, aComment);\nthis.transitionTo('blogComment', 1, 13);\n```\n\nIt is also possible to pass a URL (a string that starts with a\n`/`).\n\n```javascript\nthis.transitionTo('/');\nthis.transitionTo('/blog/post/1/comment/13');\nthis.transitionTo('/blog/posts?sort=title');\n```\n\nAn options hash with a `queryParams` property may be provided as\nthe final argument to add query parameters to the destination URL.\n\n```javascript\nthis.transitionTo('blogPost', 1, {\n  queryParams: { showComments: 'true' }\n});\n\n// if you just want to transition the query parameters without changing the route\nthis.transitionTo({ queryParams: { sort: 'date' } });\n```\n\nSee also [replaceWith](#method_replaceWith).\n\nSimple Transition Example\n\n```app/routes.js\n// ...\n\nRouter.map(function() {\n  this.route('index');\n  this.route('secret');\n  this.route('fourOhFour', { path: '*:' });\n});\n\nexport default Router;\n```\n\n```app/routes/index.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class IndexRoute extends Route {\n  @action\n  moveToSecret(context) {\n    if (authorized()) {\n      this.transitionTo('secret', context);\n    } else {\n      this.transitionTo('fourOhFour');\n    }\n  }\n}\n```\n\nTransition to a nested route\n\n```app/router.js\n// ...\n\nRouter.map(function() {\n  this.route('articles', { path: '/articles' }, function() {\n    this.route('new');\n  });\n});\n\nexport default Router;\n```\n\n```app/routes/index.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class IndexRoute extends Route {\n  @action\n  transitionToNewArticle() {\n    this.transitionTo('articles.new');\n  }\n}\n```\n\nMultiple Models Example\n\n```app/router.js\n// ...\n\nRouter.map(function() {\n  this.route('index');\n\n  this.route('breakfast', { path: ':breakfastId' }, function() {\n    this.route('cereal', { path: ':cerealId' });\n  });\n});\n\nexport default Router;\n```\n\n```app/routes/index.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class IndexRoute extends Route {\n  @action\n  moveToChocolateCereal() {\n    let cereal = { cerealId: 'ChocolateYumminess' };\n    let breakfast = { breakfastId: 'CerealAndMilk' };\n\n    this.transitionTo('breakfast.cereal', breakfast, cereal);\n  }\n}\n```\n\nNested Route with Query String Example\n\n```app/routes.js\n// ...\n\nRouter.map(function() {\n  this.route('fruits', function() {\n    this.route('apples');\n  });\n});\n\nexport default Router;\n```\n\n```app/routes/index.js\nimport Route from '@ember/routing/route';\n\nexport default class IndexRoute extends Route {\n  @action\n  transitionToApples() {\n    this.transitionTo('fruits.apples', { queryParams: { color: 'red' } });\n  }\n}\n```",
       "itemtype": "method",
       "name": "transitionTo",
@@ -9700,7 +9705,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1077,
+      "line": 1076,
       "description": "Perform a synchronous transition into another route without attempting\nto resolve promises, update the URL, or abort any currently active\nasynchronous transitions (i.e. regular transitions caused by\n`transitionTo` or URL changes).\n\nThis method is handy for performing intermediate transitions on the\nway to a final destination route, and is called internally by the\ndefault implementations of the `error` and `loading` handlers.",
       "itemtype": "method",
       "name": "intermediateTransitionTo",
@@ -9724,7 +9729,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1099,
+      "line": 1098,
       "description": "Refresh the model on this route and any child routes, firing the\n`beforeModel`, `model`, and `afterModel` hooks in a similar fashion\nto how routes are entered when transitioning in from other route.\nThe current route params (e.g. `article_id`) will be passed in\nto the respective model hooks, and if a different model is returned,\n`setupController` and associated route hooks will re-fire as well.\n\nAn example usage of this method is re-querying the server for the\nlatest information using the same parameters as when the route\nwas first entered.\n\nNote that this will cause `model` hooks to fire even on routes\nthat were provided a model object when the route was initially\nentered.",
       "itemtype": "method",
       "name": "refresh",
@@ -9740,7 +9745,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1125,
+      "line": 1124,
       "description": "Transition into another route while replacing the current URL, if possible.\nThis will replace the current history entry instead of adding a new one.\nBeside that, it is identical to `transitionTo` in all other respects. See\n'transitionTo' for additional information regarding multiple models.\n\nExample\n\n```app/router.js\n// ...\n\nRouter.map(function() {\n  this.route('index');\n  this.route('secret');\n});\n\nexport default Router;\n```\n\n```app/routes/secret.js\nimport Route from '@ember/routing/route';\n\nexport default class SecretRoute Route {\n  afterModel() {\n    if (!authorized()){\n      this.replaceWith('index');\n    }\n  }\n}\n```",
       "itemtype": "method",
       "name": "replaceWith",
@@ -9776,7 +9781,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1173,
+      "line": 1172,
       "description": "This hook is the entry point for router.js",
       "access": "private",
       "tagname": "",
@@ -9787,7 +9792,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1248,
+      "line": 1247,
       "description": "This hook is the first of the route entry validation hooks\ncalled when an attempt is made to transition into a route\nor one of its children. It is called before `model` and\n`afterModel`, and is appropriate for cases when:\n\n1) A decision can be made to redirect elsewhere without\n   needing to resolve the model first.\n2) Any async operations need to occur first before the\n   model is attempted to be resolved.\n\nThis hook is provided the current `transition` attempt\nas a parameter, which can be used to `.abort()` the transition,\nsave it for a later `.retry()`, or retrieve values set\non it from a previous hook. You can also just call\n`this.transitionTo` to another route to implicitly\nabort the `transition`.\n\nYou can return a promise from this hook to pause the\ntransition until the promise resolves (or rejects). This could\nbe useful, for instance, for retrieving async code from\nthe server that is required to enter a route.",
       "itemtype": "method",
       "name": "beforeModel",
@@ -9810,7 +9815,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1283,
+      "line": 1282,
       "description": "This hook is called after this route's model has resolved.\nIt follows identical async/promise semantics to `beforeModel`\nbut is provided the route's resolved model in addition to\nthe `transition`, and is therefore suited to performing\nlogic that can only take place after the model has already\nresolved.\n\n```app/routes/posts.js\nimport Route from '@ember/routing/route';\n\nexport default class PostsRoute extends Route {\n  afterModel(posts, transition) {\n    if (posts.get('length') === 1) {\n      this.transitionTo('post.show', posts.get('firstObject'));\n    }\n  }\n}\n```\n\nRefer to documentation for `beforeModel` for a description\nof transition-pausing semantics when a promise is returned\nfrom this hook.",
       "itemtype": "method",
       "name": "afterModel",
@@ -9838,7 +9843,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1321,
+      "line": 1320,
       "description": "A hook you can implement to optionally redirect to another route.\n\nCalling `this.transitionTo` from inside of the `redirect` hook will\nabort the current transition (into the route that has implemented `redirect`).\n\n`redirect` and `afterModel` behave very similarly and are\ncalled almost at the same time, but they have an important\ndistinction when calling `this.transitionTo` to a child route\nof the current route. From `afterModel`, this new transition\ninvalidates the current transition, causing `beforeModel`,\n`model`, and `afterModel` hooks to be called again. But the\nsame transition started from `redirect` does _not_ invalidate\nthe current transition. In other words, by the time the `redirect`\nhook has been called, both the resolved model and the attempted\nentry into this route are considered fully validated.",
       "itemtype": "method",
       "name": "redirect",
@@ -9862,7 +9867,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1346,
+      "line": 1345,
       "description": "Called when the context is changed by router.js.",
       "access": "private",
       "tagname": "",
@@ -9873,7 +9878,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1356,
+      "line": 1355,
       "description": "A hook you can implement to convert the URL into the model for\nthis route.\n\n```app/router.js\n// ...\n\nRouter.map(function() {\n  this.route('post', { path: '/posts/:post_id' });\n});\n\nexport default Router;\n```\n\nThe model for the `post` route is `store.findRecord('post', params.post_id)`.\n\nBy default, if your route has a dynamic segment ending in `_id`:\n\n* The model class is determined from the segment (`post_id`'s\n  class is `App.Post`)\n* The find method is called on the model class with the value of\n  the dynamic segment.\n\nNote that for routes with dynamic segments, this hook is not always\nexecuted. If the route is entered through a transition (e.g. when\nusing the `link-to` Handlebars helper or the `transitionTo` method\nof routes), and a model context is already provided this hook\nis not called.\n\nA model context does not include a primitive string or number,\nwhich does cause the model hook to be called.\n\nRoutes without dynamic segments will always execute the model hook.\n\n```javascript\n// no dynamic segment, model hook always called\nthis.transitionTo('posts');\n\n// model passed in, so model hook not called\nthePost = store.findRecord('post', 1);\nthis.transitionTo('post', thePost);\n\n// integer passed in, model hook is called\nthis.transitionTo('post', 1);\n\n// model id passed in, model hook is called\n// useful for forcing the hook to execute\nthePost = store.findRecord('post', 1);\nthis.transitionTo('post', thePost.id);\n```\n\nThis hook follows the asynchronous/promise semantics\ndescribed in the documentation for `beforeModel`. In particular,\nif a promise returned from `model` fails, the error will be\nhandled by the `error` hook on `Route`.\n\nExample\n\n```app/routes/post.js\nimport Route from '@ember/routing/route';\n\nexport default class PostRoute extends Route {\n  model(params) {\n    return this.store.findRecord('post', params.post_id);\n  }\n}\n```",
       "itemtype": "method",
       "name": "model",
@@ -9901,7 +9906,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1471,
+      "line": 1470,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -9927,7 +9932,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1484,
+      "line": 1483,
       "itemtype": "method",
       "name": "findModel",
       "params": [
@@ -9949,7 +9954,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1495,
+      "line": 1494,
       "description": "A hook you can use to setup the controller for the current route.\n\nThis method is called with the controller for the current route and the\nmodel supplied by the `model` hook.\n\nBy default, the `setupController` hook sets the `model` property of\nthe controller to the specified `model` when it is not `undefined`.\n\nIf you implement the `setupController` hook in your Route, it will\nprevent this default behavior. If you want to preserve that behavior\nwhen implementing your `setupController` function, make sure to call\n`super`:\n\n```app/routes/photos.js\nimport Route from '@ember/routing/route';\n\nexport default class PhotosRoute extends Route {\n  model() {\n    return this.store.findAll('photo');\n  }\n\n  setupController(controller, model) {\n    super.setupController(controller, model);\n\n    this.controllerFor('application').set('showingPhotos', true);\n  }\n}\n```\n\nThe provided controller will be one resolved based on the name\nof this route.\n\nIf no explicit controller is defined, Ember will automatically create one.\n\nAs an example, consider the router:\n\n```app/router.js\n// ...\n\nRouter.map(function() {\n  this.route('post', { path: '/posts/:post_id' });\n});\n\nexport default Router;\n```\n\nIf you have defined a file for the post controller,\nthe framework will use it.\nIf it is not defined, a basic `Controller` instance would be used.",
       "example": [
         " Behavior of a basic Controller\n\n```app/routes/post.js\nimport Route from '@ember/routing/route';\n\nexport default class PostRoute extends Route {\n  setupController(controller, model) {\n    controller.set('model', model);\n  }\n});\n```"
@@ -9982,7 +9987,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1571,
+      "line": 1570,
       "description": "Returns the controller of the current route, or a parent (or any ancestor)\nroute in a route hierarchy.\n\nThe controller instance must already have been created, either through entering the\nassociated route or using `generateController`.\n\n```app/routes/post.js\nimport Route from '@ember/routing/route';\n\nexport default class PostRoute extends Route {\n  setupController(controller, post) {\n    super.setupController(controller, post);\n\n    this.controllerFor('posts').set('currentPost', post);\n  }\n}\n```",
       "itemtype": "method",
       "name": "controllerFor",
@@ -10005,7 +10010,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1625,
+      "line": 1624,
       "description": "Generates a controller for a route.\n\nExample\n\n```app/routes/post.js\nimport Route from '@ember/routing/route';\n\nexport default class Post extends Route {\n  setupController(controller, post) {\n    super.setupController(controller, post);\n\n    this.generateController('posts');\n  }\n}\n```",
       "itemtype": "method",
       "name": "generateController",
@@ -10023,7 +10028,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1653,
+      "line": 1652,
       "description": "Returns the resolved model of a parent (or any ancestor) route\nin a route hierarchy.  During a transition, all routes\nmust resolve a model object, and if a route\nneeds access to a parent route's model in order to\nresolve a model (or just reuse the model from a parent),\nit can call `this.modelFor(theNameOfParentRoute)` to\nretrieve it. If the ancestor route's model was a promise,\nits resolved result is returned.\n\nExample\n\n```app/router.js\n// ...\n\nRouter.map(function() {\n  this.route('post', { path: '/posts/:post_id' }, function() {\n    this.route('comments');\n  });\n});\n\nexport default Router;\n```\n\n```app/routes/post/comments.js\nimport Route from '@ember/routing/route';\n\nexport default class PostCommentsRoute extends Route {\n  model() {\n    let post = this.modelFor('post');\n\n    return post.comments;\n  }\n}\n```",
       "itemtype": "method",
       "name": "modelFor",
@@ -10046,7 +10051,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1725,
+      "line": 1724,
       "description": "`this[RENDER]` is used to render a template into a region of another template\n(indicated by an `{{outlet}}`).",
       "itemtype": "method",
       "name": "this[RENDER]",
@@ -10096,7 +10101,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1752,
+      "line": 1751,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -10106,7 +10111,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1765,
+      "line": 1764,
       "description": "Allows you to produce custom metadata for the route.\nThe return value of this method will be attached to\nits corresponding RouteInfoWithAttributes object.\n\nExample\n\n```app/routes/posts/index.js\nimport Route from '@ember/routing/route';\n\nexport default class PostsIndexRoute extends Route {\n  buildRouteInfoMetadata() {\n    return { title: 'Posts Page' }\n  }\n}\n```\n\n```app/routes/application.js\nimport Route from '@ember/routing/route';\nimport { service } from '@ember/service';\n\nexport default class ApplicationRoute extends Route {\n  @service router\n\n  constructor() {\n    super(...arguments);\n\n    this.router.on('routeDidChange', transition => {\n      document.title = transition.to.metadata.title;\n      // would update document's title to \"Posts Page\"\n    });\n  }\n}\n```",
       "itemtype": "method",
       "name": "buildRouteInfoMetadata",
@@ -10121,7 +10126,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1816,
+      "line": 1815,
       "description": "Store property provides a hook for data persistence libraries to inject themselves.\n\nBy default, this store property provides the exact same functionality previously\nin the model hook.\n\nCurrently, the required interface is:\n\n`store.find(modelName, findArguments)`",
       "itemtype": "property",
       "name": "store",
@@ -10133,7 +10138,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1882,
+      "line": 1881,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -10143,7 +10148,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 2021,
+      "line": 2020,
       "description": "Sends an action to the router, which will delegate it to the currently\nactive route hierarchy per the bubbling rules explained under `actions`.\n\nExample\n\n```app/router.js\n// ...\n\nRouter.map(function() {\n  this.route('index');\n});\n\nexport default Router;\n```\n\n```app/routes/application.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class ApplicationRoute extends Route {\n  @action\n  track(arg) {\n    console.log(arg, 'was clicked');\n  }\n}\n```\n\n```app/routes/index.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class IndexRoute extends Route {\n  @action\n  trackIfDebug(arg) {\n    if (debug) {\n      this.send('track', arg);\n    }\n  }\n}\n```",
       "itemtype": "method",
       "name": "send",
@@ -10167,7 +10172,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 2406,
+      "line": 2405,
       "description": "The controller associated with this route.\n\nExample\n\n```app/routes/form.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class FormRoute extends Route {\n  @action\n  willTransition(transition) {\n    if (this.controller.get('userHasEnteredData') &&\n        !confirm('Are you sure you want to abandon progress?')) {\n      transition.abort();\n    } else {\n      // Bubble the `willTransition` action so that\n      // parent routes can decide whether or not to abort.\n      return true;\n    }\n  }\n}\n```",
       "itemtype": "property",
       "name": "controller",
@@ -10180,7 +10185,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 2437,
+      "line": 2436,
       "description": "This action is called when one or more query params have changed. Bubbles.",
       "itemtype": "method",
       "name": "queryParamsDidChange",
@@ -10212,7 +10217,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 151,
+      "line": 147,
       "description": "Represents the URL of the root of the application, often '/'. This prefix is\n assumed on all routes defined on this router.",
       "itemtype": "property",
       "name": "rootURL",
@@ -10224,7 +10229,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 162,
+      "line": 158,
       "description": "The `location` property determines the type of URL's that your\n application will use.\n\n The following location types are currently available:\n\n * `history` - use the browser's history API to make the URLs look just like any standard URL\n * `hash` - use `#` to separate the server part of the URL from the Ember part: `/blog/#/posts/new`\n * `none` - do not store the Ember URL in the actual browser URL (mainly used for testing)\n * `auto` - use the best option based on browser capabilities: `history` if possible, then `hash` if possible, otherwise `none`\n\n This value is defaulted to `auto` by the `locationType` setting of `/config/environment.js`",
       "itemtype": "property",
       "name": "location",
@@ -10239,7 +10244,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 220,
+      "line": 216,
       "description": "The `Router.map` function allows you to define mappings from URLs to routes\nin your application. These mappings are defined within the\nsupplied callback function using `this.route`.\n\nThe first parameter is the name of the route which is used by default as the\npath name as well.\n\nThe second parameter is the optional options hash. Available options are:\n\n  * `path`: allows you to provide your own path as well as mark dynamic\n    segments.\n  * `resetNamespace`: false by default; when nesting routes, ember will\n    combine the route names to form the fully-qualified route name, which is\n    used with `{{link-to}}` or manually transitioning to routes. Setting\n    `resetNamespace: true` will cause the route not to inherit from its\n    parent route's names. This is handy for preventing extremely long route names.\n    Keep in mind that the actual URL path behavior is still retained.\n\nThe third parameter is a function, which can be used to nest routes.\nNested routes, by default, will have the parent route tree's route name and\npath prepended to it's own.\n\n```app/router.js\nRouter.map(function(){\n  this.route('post', { path: '/post/:post_id' }, function() {\n    this.route('edit');\n    this.route('comments', { resetNamespace: true }, function() {\n      this.route('new');\n    });\n  });\n});\n```",
       "itemtype": "method",
       "name": "map",
@@ -10256,7 +10261,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 555,
+      "line": 551,
       "description": "Initializes the current router instance and sets up the change handling\nevent listeners used by the instances `location` implementation.\n\nA property named `initialURL` will be used to determine the initial URL.\nIf no value is found `/` will be used.",
       "itemtype": "method",
       "name": "startRouting",
@@ -10267,7 +10272,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 678,
+      "line": 674,
       "description": "Transition the application into another route. The route may\nbe either a single route or route path:",
       "itemtype": "method",
       "name": "transitionTo",
@@ -10301,7 +10306,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 723,
+      "line": 719,
       "description": "Similar to `transitionTo`, but instead of adding the destination to the browser's URL history,\nit replaces the entry for the current route.\nWhen the user clicks the \"back\" button in the browser, there will be fewer steps.\nThis is most commonly used to manage redirects in a way that does not cause confusing additions\nto the user's browsing history.",
       "itemtype": "method",
       "name": "replaceWith",
@@ -10335,7 +10340,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 750,
+      "line": 746,
       "description": "Determines if the supplied route is currently active.",
       "itemtype": "method",
       "name": "isActive",
@@ -10356,7 +10361,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 762,
+      "line": 758,
       "description": "An alternative form of `isActive` that doesn't require\nmanual concatenation of the arguments into a single\narray.",
       "itemtype": "method",
       "name": "isActiveIntent",
@@ -10386,7 +10391,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 784,
+      "line": 780,
       "description": "Does this router instance have the given route.",
       "itemtype": "method",
       "name": "hasRoute",
@@ -10401,7 +10406,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 795,
+      "line": 791,
       "description": "Resets the state of the router by clearing the current route\nhandlers and deactivating them.",
       "access": "private",
       "tagname": "",
@@ -10412,7 +10417,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 943,
+      "line": 939,
       "description": "Serializes the given query params according to their QP meta information.",
       "access": "private",
       "tagname": "",
@@ -10439,7 +10444,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 973,
+      "line": 969,
       "description": "Serializes the value of a query parameter based on a type",
       "access": "private",
       "tagname": "",
@@ -10462,7 +10467,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 991,
+      "line": 987,
       "description": "Deserializes the given query params according to their QP meta information.",
       "access": "private",
       "tagname": "",
@@ -10489,7 +10494,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1019,
+      "line": 1015,
       "description": "Deserializes the value of a query parameter based on a default type",
       "access": "private",
       "tagname": "",
@@ -10512,7 +10517,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1040,
+      "line": 1036,
       "description": "Removes (prunes) any query params with default values from the given QP\nobject. Default values are determined from the QP meta information per key.",
       "access": "private",
       "tagname": "",
@@ -10539,7 +10544,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1121,
+      "line": 1117,
       "description": "Prepares the query params for a URL or Transition. Restores any undefined QP\nkeys/values, serializes all values, and then prunes any default values.",
       "access": "private",
       "tagname": "",
@@ -10576,7 +10581,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1148,
+      "line": 1144,
       "description": "Returns the meta information for the query params of a given route. This\nwill be overridden to allow support for lazy routes.",
       "access": "private",
       "tagname": "",
@@ -10598,7 +10603,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1162,
+      "line": 1158,
       "description": "Returns a merged query params meta object for a given set of routeInfos.\nUseful for knowing what query params are available for a given route hierarchy.",
       "access": "private",
       "tagname": "",
@@ -10620,7 +10625,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1224,
+      "line": 1220,
       "description": "Maps all query param keys to their fully scoped property name of the form\n`controllerName:propName`.",
       "access": "private",
       "tagname": "",
@@ -10652,7 +10657,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1262,
+      "line": 1258,
       "description": "Hydrates (adds/restores) any query params that have pre-existing values into\nthe given queryParams hash. This is what allows query params to be \"sticky\"\nand restore their last known values for their scope.",
       "access": "private",
       "tagname": "",
@@ -10679,7 +10684,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1433,
+      "line": 1429,
       "description": "Handles updating the paths and notifying any listeners of the URL\nchange.\n\nTriggers the router level `didTransition` hook.\n\nFor example, to notify google analytics when the route changes,\nyou could use this hook.  (Note: requires also including GA scripts, etc.)\n\n```javascript\nimport config from './config/environment';\nimport EmberRouter from '@ember/routing/router';\nimport { service } from '@ember/service';\n\nlet Router = EmberRouter.extend({\n  location: config.locationType,\n\n  router: service(),\n\n  didTransition: function() {\n    this._super(...arguments);\n\n    ga('send', 'pageview', {\n      page: this.router.currentURL,\n      title: this.router.currentRouteName,\n    });\n  }\n});\n```",
       "itemtype": "method",
       "name": "didTransition",
@@ -10691,7 +10696,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1470,
+      "line": 1466,
       "description": "Handles notifying any listeners of an impending URL\nchange.\n\nTriggers the router level `willTransition` hook.",
       "itemtype": "method",
       "name": "willTransition",
@@ -10703,7 +10708,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1483,
+      "line": 1479,
       "description": "Represents the current URL.",
       "itemtype": "property",
       "name": "url",
@@ -10715,7 +10720,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1650,
+      "line": 1646,
       "description": "Finds the name of the substate route if it exists for the given route. A\nsubstate route is of the form `route_state`, such as `foo_loading`.",
       "access": "private",
       "tagname": "",
@@ -10740,7 +10745,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1671,
+      "line": 1667,
       "description": "Finds the name of the state route if it exists for the given route. A state\nroute is of the form `route.state`, such as `foo.loading`. Properly Handles\n`application` named routes.",
       "access": "private",
       "tagname": "",
@@ -10765,7 +10770,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1693,
+      "line": 1689,
       "description": "Determines whether or not a route has been defined by checking that the route\nis in the Router's map and the owner has a registration for that route.",
       "access": "private",
       "tagname": "",
@@ -11060,7 +11065,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/-proxy.ts",
-      "line": 71,
+      "line": 72,
       "description": "The object whose properties will be forwarded.",
       "itemtype": "property",
       "name": "content",
@@ -11074,7 +11079,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/-proxy.ts",
-      "line": 93,
+      "line": 94,
       "description": "The object whose properties will be forwarded.",
       "itemtype": "property",
       "name": "content",
@@ -12313,13 +12318,13 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/container_proxy.ts",
-      "line": 26,
+      "line": 27,
       "class": "ContainerProxyMixin",
       "module": "ember"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/container_proxy.ts",
-      "line": 30,
+      "line": 31,
       "description": "The container stores state.",
       "access": "private",
       "tagname": "",
@@ -12331,7 +12336,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/container_proxy.ts",
-      "line": 38,
+      "line": 39,
       "description": "Returns an object that can be used to provide an owner to a\nmanually created instance.\n\nExample:\n\n```\nimport { getOwner } from '@ember/application';\n\nlet owner = getOwner(this);\n\nUser.create(\n  owner.ownerInjection(),\n  { username: 'rwjblue' }\n)\n```",
       "access": "public",
       "tagname": "",
@@ -12347,7 +12352,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/container_proxy.ts",
-      "line": 64,
+      "line": 65,
       "description": "Given a fullName return a corresponding instance.\n\nThe default behavior is for lookup to return a singleton instance.\nThe singleton is scoped to the container, allowing multiple containers\nto all have their own locally scoped singletons.\n\n```javascript\nlet registry = new Registry();\nlet container = registry.container();\n\nregistry.register('api:twitter', Twitter);\n\nlet twitter = container.lookup('api:twitter');\n\ntwitter instanceof Twitter; // => true\n\n// by default the container will return singletons\nlet twitter2 = container.lookup('api:twitter');\ntwitter2 instanceof Twitter; // => true\n\ntwitter === twitter2; //=> true\n```\n\nIf singletons are not wanted an optional flag can be provided at lookup.\n\n```javascript\nlet registry = new Registry();\nlet container = registry.container();\n\nregistry.register('api:twitter', Twitter);\n\nlet twitter = container.lookup('api:twitter', { singleton: false });\nlet twitter2 = container.lookup('api:twitter', { singleton: false });\n\ntwitter === twitter2; //=> false\n```",
       "access": "public",
       "tagname": "",
@@ -12374,7 +12379,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/container_proxy.ts",
-      "line": 125,
+      "line": 126,
       "description": "Given a fullName return a factory manager.\n\n This method returns a manager which can be used for introspection of the\n factory's class or for the creation of factory instances with initial\n properties. The manager is an object with the following properties:\n\n * `class` - The registered or resolved class.\n * `create` - A function that will create an instance of the class with\n   any dependencies injected.\n\n For example:\n\n ```javascript\n import { getOwner } from '@ember/application';\n\n let owner = getOwner(otherInstance);\n // the owner is commonly the `applicationInstance`, and can be accessed via\n // an instance initializer.\n\n let factory = owner.factoryFor('service:bespoke');\n\n factory.class;\n // The registered or resolved class. For example when used with an Ember-CLI\n // app, this would be the default export from `app/services/bespoke.js`.\n\n let instance = factory.create({\n   someProperty: 'an initial property value'\n });\n // Create an instance with any injections and the passed options as\n // initial properties.\n ```\n\n Any instances created via the factory's `.create()` method *must* be destroyed\n manually by the caller of `.create()`. Typically, this is done during the creating\n objects own `destroy` or `willDestroy` methods.",
       "access": "public",
       "tagname": "",
@@ -13403,67 +13408,67 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/array_proxy.ts",
-      "line": 134,
+      "line": 128,
       "class": "ArrayProxy",
       "module": "@ember/array"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/array_proxy.ts",
-      "line": 136,
+      "line": 130,
       "class": "ArrayProxy",
       "module": "@ember/array"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/array_proxy.ts",
-      "line": 139,
+      "line": 133,
       "class": "ArrayProxy",
       "module": "@ember/array"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/array_proxy.ts",
-      "line": 141,
+      "line": 135,
       "class": "ArrayProxy",
       "module": "@ember/array"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/array_proxy.ts",
-      "line": 144,
+      "line": 138,
       "class": "ArrayProxy",
       "module": "@ember/array"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/array_proxy.ts",
-      "line": 146,
+      "line": 140,
       "class": "ArrayProxy",
       "module": "@ember/array"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/array_proxy.ts",
-      "line": 148,
+      "line": 142,
       "class": "ArrayProxy",
       "module": "@ember/array"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/array_proxy.ts",
-      "line": 150,
+      "line": 144,
       "class": "ArrayProxy",
       "module": "@ember/array"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/array_proxy.ts",
-      "line": 152,
+      "line": 146,
       "class": "ArrayProxy",
       "module": "@ember/array"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/array_proxy.ts",
-      "line": 154,
+      "line": 148,
       "class": "ArrayProxy",
       "module": "@ember/array"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/array_proxy.ts",
-      "line": 171,
+      "line": 165,
       "description": "The content array. Must be an object that implements `Array` and/or\n`MutableArray.`",
       "itemtype": "property",
       "name": "content",
@@ -13475,7 +13480,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/array_proxy.ts",
-      "line": 183,
+      "line": 177,
       "description": "Should actually retrieve the object at the specified index from the\ncontent. You can override this method in subclasses to transform the\ncontent item to something new.\n\nThis method will only be called if content is non-`null`.",
       "itemtype": "method",
       "name": "objectAtContent",
@@ -13497,7 +13502,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/array_proxy.ts",
-      "line": 211,
+      "line": 205,
       "description": "Should actually replace the specified objects on the content array.\nYou can override this method in subclasses to transform the content item\ninto something new.\n\nThis method will only be called if content is non-`null`.",
       "itemtype": "method",
       "name": "replaceContent",
@@ -13529,7 +13534,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/array_proxy.ts",
-      "line": 394,
+      "line": 388,
       "description": "The array that the proxy pretends to be. In the default `ArrayProxy`\nimplementation, this and `content` are the same. Subclasses of `ArrayProxy`\ncan override this property to provide things like sorting and filtering.",
       "itemtype": "property",
       "name": "arrangedContent",
@@ -13540,13 +13545,13 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.ts",
-      "line": 236,
+      "line": 235,
       "class": "CoreObject",
       "module": "@ember/object"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.ts",
-      "line": 320,
+      "line": 319,
       "description": "An overridable method called when objects are instantiated. By default,\ndoes nothing unless it is overridden during class definition.\n\nExample:\n\n```javascript\nimport EmberObject from '@ember/object';\n\nconst Person = EmberObject.extend({\n  init() {\n    alert(`Name is ${this.get('name')}`);\n  }\n});\n\nlet steve = Person.create({\n  name: 'Steve'\n});\n\n// alerts 'Name is Steve'.\n```\n\nNOTE: If you do override `init` for a framework class like `Component`\nfrom `@ember/component`, be sure to call `this._super(...arguments)`\nin your `init` declaration!\nIf you don't, Ember may not have an opportunity to\ndo important setup work, and you'll see strange behavior in your\napplication.",
       "itemtype": "method",
       "name": "init",
@@ -13557,7 +13562,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.ts",
-      "line": 354,
+      "line": 353,
       "description": "Defines the properties that will be concatenated from the superclass\n(instead of overridden).\n\nBy default, when you extend an Ember class a property defined in\nthe subclass overrides a property with the same name that is defined\nin the superclass. However, there are some cases where it is preferable\nto build up a property's value by combining the superclass' property\nvalue with the subclass' value. An example of this in use within Ember\nis the `classNames` property of `Component` from `@ember/component`.\n\nHere is some sample code showing the difference between a concatenated\nproperty and a normal one:\n\n```javascript\nimport EmberObject from '@ember/object';\n\nconst Bar = EmberObject.extend({\n  // Configure which properties to concatenate\n  concatenatedProperties: ['concatenatedProperty'],\n\n  someNonConcatenatedProperty: ['bar'],\n  concatenatedProperty: ['bar']\n});\n\nconst FooBar = Bar.extend({\n  someNonConcatenatedProperty: ['foo'],\n  concatenatedProperty: ['foo']\n});\n\nlet fooBar = FooBar.create();\nfooBar.get('someNonConcatenatedProperty'); // ['foo']\nfooBar.get('concatenatedProperty'); // ['bar', 'foo']\n```\n\nThis behavior extends to object creation as well. Continuing the\nabove example:\n\n```javascript\nlet fooBar = FooBar.create({\n  someNonConcatenatedProperty: ['baz'],\n  concatenatedProperty: ['baz']\n})\nfooBar.get('someNonConcatenatedProperty'); // ['baz']\nfooBar.get('concatenatedProperty'); // ['bar', 'foo', 'baz']\n```\n\nAdding a single property that is not an array will just add it in the array:\n\n```javascript\nlet fooBar = FooBar.create({\n  concatenatedProperty: 'baz'\n})\nview.get('concatenatedProperty'); // ['bar', 'foo', 'baz']\n```\n\nUsing the `concatenatedProperties` property, we can tell Ember to mix the\ncontent of the properties.\n\nIn `Component` the `classNames`, `classNameBindings` and\n`attributeBindings` properties are concatenated.\n\nThis feature is available for you to use throughout the Ember object model,\nalthough typical app developers are likely to use it infrequently. Since\nit changes expectations about behavior of properties, you should properly\ndocument its usage in each individual concatenated property (to not\nmislead your users to think they can override the property in a subclass).",
       "itemtype": "property",
       "name": "concatenatedProperties",
@@ -13570,7 +13575,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.ts",
-      "line": 428,
+      "line": 427,
       "description": "Defines the properties that will be merged from the superclass\n(instead of overridden).\n\nBy default, when you extend an Ember class a property defined in\nthe subclass overrides a property with the same name that is defined\nin the superclass. However, there are some cases where it is preferable\nto build up a property's value by merging the superclass property value\nwith the subclass property's value. An example of this in use within Ember\nis the `queryParams` property of routes.\n\nHere is some sample code showing the difference between a merged\nproperty and a normal one:\n\n```javascript\nimport EmberObject from '@ember/object';\n\nconst Bar = EmberObject.extend({\n  // Configure which properties are to be merged\n  mergedProperties: ['mergedProperty'],\n\n  someNonMergedProperty: {\n    nonMerged: 'superclass value of nonMerged'\n  },\n  mergedProperty: {\n    page: { replace: false },\n    limit: { replace: true }\n  }\n});\n\nconst FooBar = Bar.extend({\n  someNonMergedProperty: {\n    completelyNonMerged: 'subclass value of nonMerged'\n  },\n  mergedProperty: {\n    limit: { replace: false }\n  }\n});\n\nlet fooBar = FooBar.create();\n\nfooBar.get('someNonMergedProperty');\n// => { completelyNonMerged: 'subclass value of nonMerged' }\n//\n// Note the entire object, including the nonMerged property of\n// the superclass object, has been replaced\n\nfooBar.get('mergedProperty');\n// => {\n//   page: {replace: false},\n//   limit: {replace: false}\n// }\n//\n// Note the page remains from the superclass, and the\n// `limit` property's value of `false` has been merged from\n// the subclass.\n```\n\nThis behavior is not available during object `create` calls. It is only\navailable at `extend` time.\n\nIn `Route` the `queryParams` property is merged.\n\nThis feature is available for you to use throughout the Ember object model,\nalthough typical app developers are likely to use it infrequently. Since\nit changes expectations about behavior of properties, you should properly\ndocument its usage in each individual merged property (to not\nmislead your users to think they can override the property in a subclass).",
       "itemtype": "property",
       "name": "mergedProperties",
@@ -13583,7 +13588,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.ts",
-      "line": 503,
+      "line": 502,
       "description": "Destroyed object property flag.\n\nif this property is `true` the observers and bindings were already\nremoved by the effect of calling the `destroy()` method.",
       "itemtype": "property",
       "name": "isDestroyed",
@@ -13595,7 +13600,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.ts",
-      "line": 521,
+      "line": 520,
       "description": "Destruction scheduled flag. The `destroy()` method has been called.\n\nThe object stays intact until the end of the run loop at which point\nthe `isDestroyed` flag is set.",
       "itemtype": "property",
       "name": "isDestroying",
@@ -13607,7 +13612,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.ts",
-      "line": 539,
+      "line": 538,
       "description": "Destroys an object by setting the `isDestroyed` flag and removing its\nmetadata, which effectively destroys observers and bindings.\n\nIf you try to set a property on a destroyed object, an exception will be\nraised.\n\nNote that destruction is scheduled for the end of the run loop and does not\nhappen immediately.  It will set an isDestroying flag immediately.",
       "itemtype": "method",
       "name": "destroy",
@@ -13622,7 +13627,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.ts",
-      "line": 566,
+      "line": 565,
       "description": "Override to implement teardown.",
       "itemtype": "method",
       "name": "willDestroy",
@@ -13633,7 +13638,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.ts",
-      "line": 574,
+      "line": 573,
       "description": "Returns a string representation which attempts to provide more information\nthan Javascript's `toString` typically does, in a generic way for all Ember\nobjects.\n\n```javascript\nimport EmberObject from '@ember/object';\n\nconst Person = EmberObject.extend();\nperson = Person.create();\nperson.toString(); //=> \"<Person:ember1024>\"\n```\n\nIf the object's class is not defined on an Ember namespace, it will\nindicate it is a subclass of the registered superclass:\n\n```javascript\nconst Student = Person.extend();\nlet student = Student.create();\nstudent.toString(); //=> \"<(subclass of Person):ember1025>\"\n```\n\nIf the method `toStringExtension` is defined, its return value will be\nincluded in the output.\n\n```javascript\nconst Teacher = Person.extend({\n  toStringExtension() {\n    return this.get('fullName');\n  }\n});\nteacher = Teacher.create();\nteacher.toString(); //=> \"<Teacher:ember1026:Tom Dale>\"\n```",
       "itemtype": "method",
       "name": "toString",
@@ -13648,7 +13653,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.ts",
-      "line": 619,
+      "line": 618,
       "description": "Creates a new subclass.\n\n```javascript\nimport EmberObject from '@ember/object';\n\nconst Person = EmberObject.extend({\n  say(thing) {\n    alert(thing);\n   }\n});\n```\n\nThis defines a new subclass of EmberObject: `Person`. It contains one method: `say()`.\n\nYou can also create a subclass from any existing class by calling its `extend()` method.\nFor example, you might want to create a subclass of Ember's built-in `Component` class:\n\n```javascript\nimport Component from '@ember/component';\n\nconst PersonComponent = Component.extend({\n  tagName: 'li',\n  classNameBindings: ['isAdministrator']\n});\n```\n\nWhen defining a subclass, you can override methods but still access the\nimplementation of your parent class by calling the special `_super()` method:\n\n```javascript\nimport EmberObject from '@ember/object';\n\nconst Person = EmberObject.extend({\n  say(thing) {\n    let name = this.get('name');\n    alert(`${name} says: ${thing}`);\n  }\n});\n\nconst Soldier = Person.extend({\n  say(thing) {\n    this._super(`${thing}, sir!`);\n  },\n  march(numberOfHours) {\n    alert(`${this.get('name')} marches for ${numberOfHours} hours.`);\n  }\n});\n\nlet yehuda = Soldier.create({\n  name: 'Yehuda Katz'\n});\n\nyehuda.say('Yes');  // alerts \"Yehuda Katz says: Yes, sir!\"\n```\n\nThe `create()` on line #17 creates an *instance* of the `Soldier` class.\nThe `extend()` on line #8 creates a *subclass* of `Person`. Any instance\nof the `Person` class will *not* have the `march()` method.\n\nYou can also pass `Mixin` classes to add additional properties to the subclass.\n\n```javascript\nimport EmberObject from '@ember/object';\nimport Mixin from '@ember/object/mixin';\n\nconst Person = EmberObject.extend({\n  say(thing) {\n    alert(`${this.get('name')} says: ${thing}`);\n  }\n});\n\nconst SingingMixin = Mixin.create({\n  sing(thing) {\n    alert(`${this.get('name')} sings: la la la ${thing}`);\n  }\n});\n\nconst BroadwayStar = Person.extend(SingingMixin, {\n  dance() {\n    alert(`${this.get('name')} dances: tap tap tap tap `);\n  }\n});\n```\n\nThe `BroadwayStar` class contains three methods: `say()`, `sing()`, and `dance()`.",
       "itemtype": "method",
       "name": "extend",
@@ -13676,7 +13681,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.ts",
-      "line": 723,
+      "line": 722,
       "description": "Creates an instance of a class. Accepts either no arguments, or an object\ncontaining values to initialize the newly instantiated object with.\n\n```javascript\nimport EmberObject from '@ember/object';\n\nconst Person = EmberObject.extend({\n  helloWorld() {\n    alert(`Hi, my name is ${this.get('name')}`);\n  }\n});\n\nlet tom = Person.create({\n  name: 'Tom Dale'\n});\n\ntom.helloWorld(); // alerts \"Hi, my name is Tom Dale\".\n```\n\n`create` will call the `init` function if defined during\n`AnyObject.extend`\n\nIf no arguments are passed to `create`, it will not set values to the new\ninstance during initialization:\n\n```javascript\nlet noName = Person.create();\nnoName.helloWorld(); // alerts undefined\n```\n\nNOTE: For performance reasons, you cannot declare methods or computed\nproperties during `create`. You should instead declare methods and computed\nproperties when using `extend`.",
       "itemtype": "method",
       "name": "create",
@@ -13696,7 +13701,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.ts",
-      "line": 788,
+      "line": 787,
       "description": "Augments a constructor's prototype with additional\nproperties and functions:\n\n```javascript\nimport EmberObject from '@ember/object';\n\nconst MyObject = EmberObject.extend({\n  name: 'an object'\n});\n\no = MyObject.create();\no.get('name'); // 'an object'\n\nMyObject.reopen({\n  say(msg) {\n    console.log(msg);\n  }\n});\n\no2 = MyObject.create();\no2.say('hello'); // logs \"hello\"\n\no.say('goodbye'); // logs \"goodbye\"\n```\n\nTo add functions and properties to the constructor itself,\nsee `reopenClass`",
       "itemtype": "method",
       "name": "reopen",
@@ -13708,7 +13713,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.ts",
-      "line": 842,
+      "line": 841,
       "description": "Augments a constructor's own properties and functions:\n\n```javascript\nimport EmberObject from '@ember/object';\n\nconst MyObject = EmberObject.extend({\n  name: 'an object'\n});\n\nMyObject.reopenClass({\n  canBuild: false\n});\n\nMyObject.canBuild; // false\no = MyObject.create();\n```\n\nIn other words, this creates static properties and functions for the class.\nThese are only available on the class and not on any instance of that class.\n\n```javascript\nimport EmberObject from '@ember/object';\n\nconst Person = EmberObject.extend({\n  name: '',\n  sayHello() {\n    alert(`Hello. My name is ${this.get('name')}`);\n  }\n});\n\nPerson.reopenClass({\n  species: 'Homo sapiens',\n\n  createPerson(name) {\n    return Person.create({ name });\n  }\n});\n\nlet tom = Person.create({\n  name: 'Tom Dale'\n});\nlet yehuda = Person.createPerson('Yehuda Katz');\n\ntom.sayHello(); // \"Hello. My name is Tom Dale\"\nyehuda.sayHello(); // \"Hello. My name is Yehuda Katz\"\nalert(Person.species); // \"Homo sapiens\"\n```\n\nNote that `species` and `createPerson` are *not* valid on the `tom` and `yehuda`\nvariables. They are only valid on `Person`.\n\nTo add functions and properties to instances of\na constructor by extending the constructor's prototype\nsee `reopen`",
       "itemtype": "method",
       "name": "reopenClass",
@@ -13720,7 +13725,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.ts",
-      "line": 925,
+      "line": 924,
       "description": "In some cases, you may want to annotate computed properties with additional\nmetadata about how they function or what values they operate on. For\nexample, computed property functions may close over variables that are then\nno longer available for introspection.\n\nYou can pass a hash of these values to a computed property like this:\n\n```javascript\nimport { computed } from '@ember/object';\n\nperson: computed(function() {\n  let personId = this.get('personId');\n  return Person.create({ id: personId });\n}).meta({ type: Person })\n```\n\nOnce you've done this, you can retrieve the values saved to the computed\nproperty from your class like this:\n\n```javascript\nMyClass.metaForProperty('person');\n```\n\nThis will return the original hash that was passed to `meta()`.",
       "static": 1,
       "itemtype": "method",
@@ -13739,7 +13744,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.ts",
-      "line": 968,
+      "line": 967,
       "description": "Iterate over each computed property for the class, passing its name\nand any associated metadata (see `metaForProperty`) to the callback.",
       "static": 1,
       "itemtype": "method",
@@ -13763,7 +13768,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.ts",
-      "line": 1060,
+      "line": 1059,
       "description": "Provides lookup-time type validation for injected properties.",
       "access": "private",
       "tagname": "",
@@ -13774,7 +13779,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.ts",
-      "line": 1081,
+      "line": 1080,
       "description": "Returns a hash of property names and container names that injected\nproperties will lookup on the container lazily.",
       "itemtype": "method",
       "name": "_lazyInjections",
@@ -13789,7 +13794,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/compare.ts",
-      "line": 51,
+      "line": 52,
       "description": "Compares two javascript values and returns:\n\n - -1 if the first is smaller than the second,\n - 0 if both are equal,\n - 1 if the first is greater than the second.\n\n ```javascript\n import { compare } from '@ember/utils';\n\n compare('hello', 'hello');  // 0\n compare('abc', 'dfg');      // -1\n compare(2, 1);              // 1\n ```\n\nIf the types of the two objects are different precedence occurs in the\nfollowing order, with types earlier in the list considered `<` types\nlater in the list:\n\n - undefined\n - null\n - boolean\n - number\n - string\n - array\n - object\n - instance\n - function\n - class\n - date\n\n ```javascript\n import { compare } from '@ember/utils';\n\n compare('hello', 50);       // 1\n compare(50, 'hello');       // -1\n ```",
       "itemtype": "method",
       "name": "compare",
@@ -14539,7 +14544,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 35,
+      "line": 36,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -14556,7 +14561,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 57,
+      "line": 58,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -14573,7 +14578,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 77,
+      "line": 78,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -14590,7 +14595,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 109,
+      "line": 110,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -14607,7 +14612,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 152,
+      "line": 153,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -14624,7 +14629,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 161,
+      "line": 162,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -14641,7 +14646,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 176,
+      "line": 177,
       "description": "`getViewClientRects` provides information about the position of the border\nbox edges of a view relative to the viewport.\n\nIt is only intended to be used by development tools like the Ember Inspector\nand may not work on older browsers.",
       "access": "private",
       "tagname": "",
@@ -14659,7 +14664,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 192,
+      "line": 193,
       "description": "`getViewBoundingClientRect` provides information about the position of the\nbounding border box edges of a view relative to the viewport.\n\nIt is only intended to be used by development tools like the Ember Inspector\nand may not work on older browsers.",
       "access": "private",
       "tagname": "",
@@ -14677,7 +14682,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 208,
+      "line": 209,
       "description": "Determines if the element matches the specified selector.",
       "access": "private",
       "tagname": "",
@@ -14700,7 +14705,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/views/core_view.ts",
-      "line": 35,
+      "line": 36,
       "description": "If the view is currently inserted into the DOM of a parent view, this\nproperty will point to the parent of the view.",
       "itemtype": "property",
       "name": "parentView",
@@ -14714,7 +14719,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/views/core_view.ts",
-      "line": 74,
+      "line": 75,
       "description": "Override the default event firing from `Evented` to\nalso call methods with the given name.",
       "itemtype": "method",
       "name": "trigger",
@@ -14733,7 +14738,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.ts",
-      "line": 186,
+      "line": 188,
       "description": "This creates a registry with the default Ember naming conventions.\n\nIt also configures the registry:\n\n* registered views are created every time they are looked up (they are\n  not singletons)\n* registered templates are not factories; the registered value is\n  returned directly.\n* the router receives the application as its `namespace` property\n* all controllers receive the router as their `target` and `controllers`\n  properties\n* all controllers receive the application as their `namespace` property\n* the application view receives the application controller as its\n  `controller` property\n* the application view receives the application template as its\n  `defaultTemplate` property",
       "itemtype": "method",
       "name": "buildRegistry",
@@ -14756,7 +14761,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.ts",
-      "line": 221,
+      "line": 223,
       "description": "The root DOM element of the Application. This can be specified as an\nelement or a [selector string](https://developer.mozilla.org/en-US/docs/Learn/CSS/Building_blocks/Selectors#reference_table_of_selectors).\n\nThis is the element that will be passed to the Application's,\n`eventDispatcher`, which sets up the listeners for event delegation. Every\nview in your application should be a child of the element you specify here.",
       "itemtype": "property",
       "name": "rootElement",
@@ -14769,7 +14774,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.ts",
-      "line": 236,
+      "line": 238,
       "itemtype": "property",
       "name": "_document",
       "type": "Document | null",
@@ -14781,7 +14786,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.ts",
-      "line": 245,
+      "line": 247,
       "description": "The `Ember.EventDispatcher` responsible for delegating events to this\napplication's views.\n\nThe event dispatcher is created by the application at initialization time\nand sets up event listeners on the DOM element described by the\napplication's `rootElement` property.\n\nSee the documentation for `Ember.EventDispatcher` for more information.",
       "itemtype": "property",
       "name": "eventDispatcher",
@@ -14794,7 +14799,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.ts",
-      "line": 262,
+      "line": 264,
       "description": "The DOM events for which the event dispatcher should listen.\n\nBy default, the application's `Ember.EventDispatcher` listens\nfor a set of standard DOM events, such as `mousedown` and\n`keyup`, and delegates them to your application's `Ember.View`\ninstances.\n\nIf you would like additional bubbling events to be delegated to your\nviews, set your `Application`'s `customEvents` property\nto a hash containing the DOM event name as the key and the\ncorresponding view method name as the value. Setting an event to\na value of `null` will prevent a default event listener from being\nadded for that event.\n\nTo add new events to be listened to:\n\n```app/app.js\nimport Application from '@ember/application';\n\nlet App = Application.extend({\n  customEvents: {\n    // add support for the paste event\n    paste: 'paste'\n  }\n});\n```\n\nTo prevent default events from being listened to:\n\n```app/app.js\nimport Application from '@ember/application';\n\nlet App = Application.extend({\n  customEvents: {\n    // remove support for mouseenter / mouseleave events\n    mouseenter: null,\n    mouseleave: null\n  }\n});\n```",
       "itemtype": "property",
       "name": "customEvents",
@@ -14807,7 +14812,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.ts",
-      "line": 310,
+      "line": 312,
       "description": "Whether the application should automatically start routing and render\ntemplates to the `rootElement` on DOM ready. While default by true,\nother environments such as FastBoot or a testing harness can set this\nproperty to `false` and control the precise timing and behavior of the boot\nprocess.",
       "itemtype": "property",
       "name": "autoboot",
@@ -14820,7 +14825,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.ts",
-      "line": 324,
+      "line": 326,
       "description": "Whether the application should be configured for the legacy \"globals mode\".\nUnder this mode, the Application object serves as a global namespace for all\nclasses.\n\n```javascript\nimport Application from '@ember/application';\nimport Component from '@ember/component';\n\nlet App = Application.create({\n  ...\n});\n\nApp.Router.reopen({\n  location: 'none'\n});\n\nApp.Router.map({\n  ...\n});\n\nApp.MyComponent = Component.extend({\n  ...\n});\n```\n\nThis flag also exposes other internal APIs that assumes the existence of\na special \"default instance\", like `App.__container__.lookup(...)`.\n\nThis option is currently not configurable, its value is derived from\nthe `autoboot` flag – disabling `autoboot` also implies opting-out of\nglobals mode support, although they are ultimately orthogonal concerns.\n\nSome of the global modes features are already deprecated in 1.x. The\nexistence of this flag is to untangle the globals mode code paths from\nthe autoboot code paths, so that these legacy features can be reviewed\nfor deprecation/removal separately.\n\nForcing the (autoboot=true, _globalsMode=false) here and running the tests\nwould reveal all the places where we are still relying on these legacy\nbehavior internally (mostly just tests).",
       "itemtype": "property",
       "name": "_globalsMode",
@@ -14833,7 +14838,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.ts",
-      "line": 373,
+      "line": 375,
       "description": "An array of application instances created by `buildInstance()`. Used\ninternally to ensure that all instances get destroyed.",
       "itemtype": "property",
       "name": "_applicationInstances",
@@ -14845,7 +14850,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.ts",
-      "line": 423,
+      "line": 425,
       "description": "Create an ApplicationInstance for this application.",
       "access": "public",
       "tagname": "",
@@ -14860,7 +14865,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.ts",
-      "line": 448,
+      "line": 450,
       "description": "Start tracking an ApplicationInstance for this application.\nUsed when the ApplicationInstance is created.",
       "access": "private",
       "tagname": "",
@@ -14871,7 +14876,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.ts",
-      "line": 459,
+      "line": 461,
       "description": "Stop tracking an ApplicationInstance for this application.\nUsed when the ApplicationInstance is about to be destroyed.",
       "access": "private",
       "tagname": "",
@@ -14882,7 +14887,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.ts",
-      "line": 472,
+      "line": 474,
       "description": "Enable the legacy globals mode by allowing this application to act\nas a global namespace. See the docs on the `_globalsMode` property\nfor details.\n\nMost of these features are already deprecated in 1.x, so we can\nstop using them internally and try to remove them.",
       "access": "private",
       "tagname": "",
@@ -14893,7 +14898,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.ts",
-      "line": 519,
+      "line": 521,
       "description": "Automatically kick-off the boot process for the application once the\nDOM has become ready.\n\nThe initialization itself is scheduled on the actions queue which\nensures that code-loading finishes before booting.\n\nIf you are asynchronously loading code, you should call `deferReadiness()`\nto defer booting, and then call `advanceReadiness()` once all of your code\nhas finished loading.",
       "access": "private",
       "tagname": "",
@@ -14904,7 +14909,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.ts",
-      "line": 559,
+      "line": 561,
       "description": "This is the autoboot flow:\n\n1. Boot the app by calling `this.boot()`\n2. Create an instance (or use the `__deprecatedInstance__` in globals mode)\n3. Boot the instance by calling `instance.boot()`\n4. Invoke the `App.ready()` callback\n5. Kick-off routing on the instance\n\nIdeally, this is all we would need to do:\n\n```javascript\n_autoBoot() {\n  this.boot().then(() => {\n    let instance = (this._globalsMode) ? this.__deprecatedInstance__ : this.buildInstance();\n    return instance.boot();\n  }).then((instance) => {\n    App.ready();\n    instance.startRouting();\n  });\n}\n```\n\nUnfortunately, we cannot actually write this because we need to participate\nin the \"synchronous\" boot process. While the code above would work fine on\nthe initial boot (i.e. DOM ready), when `App.reset()` is called, we need to\nboot a new instance synchronously (see the documentation on `_bootSync()`\nfor details).\n\nBecause of this restriction, the actual logic of this method is located\ninside `didBecomeReady()`.",
       "access": "private",
       "tagname": "",
@@ -14915,7 +14920,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.ts",
-      "line": 604,
+      "line": 606,
       "description": "Use this to defer readiness until some condition is true.\n\nExample:\n\n```javascript\nimport Application from '@ember/application';\n\nlet App = Application.create();\n\nApp.deferReadiness();\n\nfetch('/auth-token')\n.then(response => response.json())\n.then(data => {\n  App.token = data.token;\n  App.advanceReadiness();\n});\n```\n\nThis allows you to perform asynchronous setup logic and defer\nbooting your application until the setup has finished.\n\nHowever, if the setup requires a loading UI, it might be better\nto use the router for this purpose.",
       "itemtype": "method",
       "name": "deferReadiness",
@@ -14926,7 +14931,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.ts",
-      "line": 654,
+      "line": 656,
       "description": "Call `advanceReadiness` after any asynchronous setup logic has completed.\nEach call to `deferReadiness` must be matched by a call to `advanceReadiness`\nor the application will never become ready and routing will not begin.",
       "itemtype": "method",
       "name": "advanceReadiness",
@@ -14940,7 +14945,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.ts",
-      "line": 693,
+      "line": 695,
       "description": "Initialize the application and return a promise that resolves with the `Application`\nobject when the boot process is complete.\n\nRun any application initializers and run the application load hook. These hooks may\nchoose to defer readiness. For example, an authentication hook might want to defer\nreadiness until the auth token has been retrieved.\n\nBy default, this method is called automatically on \"DOM ready\"; however, if autoboot\nis disabled, this is automatically called when the first application instance is\ncreated via `visit`.",
       "access": "public",
       "tagname": "",
@@ -14955,7 +14960,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.ts",
-      "line": 735,
+      "line": 737,
       "description": "Unfortunately, a lot of existing code assumes the booting process is\n\"synchronous\". Specifically, a lot of tests assumes the last call to\n`app.advanceReadiness()` or `app.reset()` will result in the app being\nfully-booted when the current runloop completes.\n\nWe would like new code (like the `visit` API) to stop making this assumption,\nso we created the asynchronous version above that returns a promise. But until\nwe have migrated all the code, we would have to expose this method for use\n*internally* in places where we need to boot an app \"synchronously\".",
       "access": "private",
       "tagname": "",
@@ -14964,7 +14969,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.ts",
-      "line": 774,
+      "line": 776,
       "description": "Reset the application. This is typically used only in tests. It cleans up\nthe application in the following order:\n\n1. Deactivate existing routes\n2. Destroy all objects in the container\n3. Create a new application container\n4. Re-route to the existing url\n\nTypical Example:\n\n```javascript\nimport Application from '@ember/application';\nlet App;\n\nrun(function() {\n  App = Application.create();\n});\n\nmodule('acceptance test', {\n  setup: function() {\n    App.reset();\n  }\n});\n\ntest('first test', function() {\n  // App is freshly reset\n});\n\ntest('second test', function() {\n  // App is again freshly reset\n});\n```\n\nAdvanced Example:\n\nOccasionally you may want to prevent the app from initializing during\nsetup. This could enable extra configuration, or enable asserting prior\nto the app becoming ready.\n\n```javascript\nimport Application from '@ember/application';\nlet App;\n\nrun(function() {\n  App = Application.create();\n});\n\nmodule('acceptance test', {\n  setup: function() {\n    run(function() {\n      App.reset();\n      App.deferReadiness();\n    });\n  }\n});\n\ntest('first test', function() {\n  ok(true, 'something before app is initialized');\n\n  run(function() {\n    App.advanceReadiness();\n  });\n\n  ok(true, 'something after app is initialized');\n});\n```",
       "itemtype": "method",
       "name": "reset",
@@ -14975,7 +14980,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.ts",
-      "line": 878,
+      "line": 880,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -14985,7 +14990,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.ts",
-      "line": 931,
+      "line": 933,
       "description": "Called when the Application has become ready, immediately before routing\nbegins. The call will be delayed until the DOM has become ready.",
       "itemtype": "event",
       "name": "ready",
@@ -14996,7 +15001,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.ts",
-      "line": 956,
+      "line": 958,
       "description": "Boot a new instance of `ApplicationInstance` for the current\napplication and navigate it to the given `url`. Returns a `Promise` that\nresolves with the instance when the initial routing and rendering is\ncomplete, or rejects with any error that occurred during the boot process.\n\nWhen `autoboot` is disabled, calling `visit` would first cause the\napplication to boot, which runs the application initializers.\n\nThis method also takes a hash of boot-time configuration options for\ncustomizing the instance's behavior. See the documentation on\n`ApplicationInstance.BootOptions` for details.\n\n`ApplicationInstance.BootOptions` is an interface class that exists\npurely to document the available options; you do not need to construct it\nmanually. Simply pass a regular JavaScript object containing of the\ndesired options:\n\n```javascript\nMyApp.visit(\"/\", { location: \"none\", rootElement: \"#container\" });\n```\n\n### Supported Scenarios\n\nWhile the `BootOptions` class exposes a large number of knobs, not all\ncombinations of them are valid; certain incompatible combinations might\nresult in unexpected behavior.\n\nFor example, booting the instance in the full browser environment\nwhile specifying a foreign `document` object (e.g. `{ isBrowser: true,\ndocument: iframe.contentDocument }`) does not work correctly today,\nlargely due to Ember's jQuery dependency.\n\nCurrently, there are three officially supported scenarios/configurations.\nUsages outside of these scenarios are not guaranteed to work, but please\nfeel free to file bug reports documenting your experience and any issues\nyou encountered to help expand support.\n\n#### Browser Applications (Manual Boot)\n\nThe setup is largely similar to how Ember works out-of-the-box. Normally,\nEmber will boot a default instance for your Application on \"DOM ready\".\nHowever, you can customize this behavior by disabling `autoboot`.\n\nFor example, this allows you to render a miniture demo of your application\ninto a specific area on your marketing website:\n\n```javascript\nimport MyApp from 'my-app';\n\n$(function() {\n  let App = MyApp.create({ autoboot: false });\n\n  let options = {\n    // Override the router's location adapter to prevent it from updating\n    // the URL in the address bar\n    location: 'none',\n\n    // Override the default `rootElement` on the app to render into a\n    // specific `div` on the page\n    rootElement: '#demo'\n  };\n\n  // Start the app at the special demo URL\n  App.visit('/demo', options);\n});\n```\n\nOr perhaps you might want to boot two instances of your app on the same\npage for a split-screen multiplayer experience:\n\n```javascript\nimport MyApp from 'my-app';\n\n$(function() {\n  let App = MyApp.create({ autoboot: false });\n\n  let sessionId = MyApp.generateSessionID();\n\n  let player1 = App.visit(`/matches/join?name=Player+1&session=${sessionId}`, { rootElement: '#left', location: 'none' });\n  let player2 = App.visit(`/matches/join?name=Player+2&session=${sessionId}`, { rootElement: '#right', location: 'none' });\n\n  Promise.all([player1, player2]).then(() => {\n    // Both apps have completed the initial render\n    $('#loading').fadeOut();\n  });\n});\n```\n\nDo note that each app instance maintains their own registry/container, so\nthey will run in complete isolation by default.\n\n#### Server-Side Rendering (also known as FastBoot)\n\nThis setup allows you to run your Ember app in a server environment using\nNode.js and render its content into static HTML for SEO purposes.\n\n```javascript\nconst HTMLSerializer = new SimpleDOM.HTMLSerializer(SimpleDOM.voidMap);\n\nfunction renderURL(url) {\n  let dom = new SimpleDOM.Document();\n  let rootElement = dom.body;\n  let options = { isBrowser: false, document: dom, rootElement: rootElement };\n\n  return MyApp.visit(options).then(instance => {\n    try {\n      return HTMLSerializer.serialize(rootElement.firstChild);\n    } finally {\n      instance.destroy();\n    }\n  });\n}\n```\n\nIn this scenario, because Ember does not have access to a global `document`\nobject in the Node.js environment, you must provide one explicitly. In practice,\nin the non-browser environment, the stand-in `document` object only needs to\nimplement a limited subset of the full DOM API. The `SimpleDOM` library is known\nto work.\n\nSince there is no DOM access in the non-browser environment, you must also\nspecify a DOM `Element` object in the same `document` for the `rootElement` option\n(as opposed to a selector string like `\"body\"`).\n\nSee the documentation on the `isBrowser`, `document` and `rootElement` properties\non `ApplicationInstance.BootOptions` for details.\n\n#### Server-Side Resource Discovery\n\nThis setup allows you to run the routing layer of your Ember app in a server\nenvironment using Node.js and completely disable rendering. This allows you\nto simulate and discover the resources (i.e. AJAX requests) needed to fulfill\na given request and eagerly \"push\" these resources to the client.\n\n```app/initializers/network-service.js\nimport BrowserNetworkService from 'app/services/network/browser';\nimport NodeNetworkService from 'app/services/network/node';\n\n// Inject a (hypothetical) service for abstracting all AJAX calls and use\n// the appropriate implementation on the client/server. This also allows the\n// server to log all the AJAX calls made during a particular request and use\n// that for resource-discovery purpose.\n\nexport function initialize(application) {\n  if (window) { // browser\n    application.register('service:network', BrowserNetworkService);\n  } else { // node\n    application.register('service:network', NodeNetworkService);\n  }\n};\n\nexport default {\n  name: 'network-service',\n  initialize: initialize\n};\n```\n\n```app/routes/post.js\nimport Route from '@ember/routing/route';\nimport { service } from '@ember/service';\n\n// An example of how the (hypothetical) service is used in routes.\n\nexport default class IndexRoute extends Route {\n  @service network;\n\n  model(params) {\n    return this.network.fetch(`/api/posts/${params.post_id}.json`);\n  }\n\n  afterModel(post) {\n    if (post.isExternalContent) {\n      return this.network.fetch(`/api/external/?url=${post.externalURL}`);\n    } else {\n      return post;\n    }\n  }\n}\n```\n\n```javascript\n// Finally, put all the pieces together\n\nfunction discoverResourcesFor(url) {\n  return MyApp.visit(url, { isBrowser: false, shouldRender: false }).then(instance => {\n    let networkService = instance.lookup('service:network');\n    return networkService.requests; // => { \"/api/posts/123.json\": \"...\" }\n  });\n}\n```",
       "access": "public",
       "tagname": "",
@@ -15071,7 +15076,7 @@
     },
     {
       "file": "packages/@ember/application/instance.ts",
-      "line": 54,
+      "line": 55,
       "description": "The `Application` for which this is an instance.",
       "itemtype": "property",
       "name": "application",
@@ -15083,7 +15088,7 @@
     },
     {
       "file": "packages/@ember/application/instance.ts",
-      "line": 62,
+      "line": 63,
       "description": "The root DOM element of the Application as an element or a\nCSS selector.",
       "access": "private",
       "tagname": "",
@@ -15095,7 +15100,7 @@
     },
     {
       "file": "packages/@ember/application/instance.ts",
-      "line": 88,
+      "line": 89,
       "description": "Overrides the base `EngineInstance._bootSync` method with concerns relevant\nto booting application (instead of engine) instances.\n\nThis method should only contain synchronous boot concerns. Asynchronous\nboot concerns should eventually be moved to the `boot` method, which\nreturns a promise.\n\nUntil all boot code has been made asynchronous, we need to continue to\nexpose this method for use *internally* in places where we need to boot an\ninstance synchronously.",
       "access": "private",
       "tagname": "",
@@ -15104,7 +15109,7 @@
     },
     {
       "file": "packages/@ember/application/instance.ts",
-      "line": 148,
+      "line": 149,
       "description": "This hook is called by the root-most Route (a.k.a. the ApplicationRoute)\nwhen it has finished creating the root View. By default, we simply take the\nview and append it to the `rootElement` specified on the Application.\n\nIn cases like FastBoot and testing, we can override this hook and implement\ncustom behavior, such as serializing to a string and sending over an HTTP\nsocket rather than appending to DOM.",
       "params": [
         {
@@ -15121,7 +15126,7 @@
     },
     {
       "file": "packages/@ember/application/instance.ts",
-      "line": 165,
+      "line": 166,
       "description": "Tells the router to start routing. The router will ask the location for the\ncurrent URL of the page to determine the initial URL to start routing to.\nTo start the app at a specific URL, call `handleURL` instead.",
       "access": "private",
       "tagname": "",
@@ -15130,7 +15135,7 @@
     },
     {
       "file": "packages/@ember/application/instance.ts",
-      "line": 176,
+      "line": 177,
       "description": "Sets up the router, initializing the child router and configuring the\nlocation before routing begins.\n\nBecause setup should only occur once, multiple calls to `setupRouter`\nbeyond the first call have no effect.\n\nThis is commonly used in order to confirm things that rely on the router\nare functioning properly from tests that are primarily rendering related.\n\nFor example, from within [ember-qunit](https://github.com/emberjs/ember-qunit)'s\n`setupRenderingTest` calling `this.owner.setupRouter()` would allow that\nrendering test to confirm that any `<LinkTo></LinkTo>`'s that are rendered\nhave the correct URL.",
       "access": "public",
       "tagname": "",
@@ -15139,7 +15144,7 @@
     },
     {
       "file": "packages/@ember/application/instance.ts",
-      "line": 197,
+      "line": 198,
       "description": "Directs the router to route to a particular URL. This is useful in tests,\nfor example, to tell the app to start at a particular URL.",
       "params": [
         {
@@ -15155,7 +15160,7 @@
     },
     {
       "file": "packages/@ember/application/instance.ts",
-      "line": 209,
+      "line": 210,
       "access": "private",
       "tagname": "",
       "class": "ApplicationInstance",
@@ -15163,7 +15168,7 @@
     },
     {
       "file": "packages/@ember/application/instance.ts",
-      "line": 231,
+      "line": 232,
       "description": "Returns the current URL of the app instance. This is useful when your\napp does not update the browsers URL bar (i.e. it uses the `'none'`\nlocation adapter).",
       "access": "public",
       "tagname": "",
@@ -15176,7 +15181,7 @@
     },
     {
       "file": "packages/@ember/application/instance.ts",
-      "line": 246,
+      "line": 247,
       "description": "Navigate the instance to a particular URL. This is useful in tests, for\nexample, or to tell the app to start at a particular URL. This method\nreturns a promise that resolves with the app instance when the transition\nis complete, or rejects if the transion was aborted due to an error.",
       "access": "public",
       "tagname": "",
@@ -15196,7 +15201,7 @@
     },
     {
       "file": "packages/@ember/application/instance.ts",
-      "line": 305,
+      "line": 306,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -15218,7 +15223,7 @@
     },
     {
       "file": "packages/@ember/application/instance.ts",
-      "line": 348,
+      "line": 349,
       "description": "Interactive mode: whether we need to set up event delegation and invoke\nlifecycle callbacks on Components.",
       "itemtype": "property",
       "name": "isInteractive",
@@ -15232,7 +15237,7 @@
     },
     {
       "file": "packages/@ember/application/instance.ts",
-      "line": 359,
+      "line": 360,
       "itemtype": "property",
       "name": "_renderMode",
       "type": "string",
@@ -15245,7 +15250,7 @@
     },
     {
       "file": "packages/@ember/application/instance.ts",
-      "line": 367,
+      "line": 368,
       "description": "Run in a full browser environment.\n\nWhen this flag is set to `false`, it will disable most browser-specific\nand interactive features. Specifically:\n\n* It does not use `jQuery` to append the root view; the `rootElement`\n  (either specified as a subsequent option or on the application itself)\n  must already be an `Element` in the given `document` (as opposed to a\n  string selector).\n\n* It does not set up an `EventDispatcher`.\n\n* It does not run any `Component` lifecycle hooks (such as `didInsertElement`).\n\n* It sets the `location` option to `\"none\"`. (If you would like to use\n  the location adapter specified in the app's router instead, you can also\n  specify `{ location: null }` to specifically opt-out.)",
       "itemtype": "property",
       "name": "isBrowser",
@@ -15259,7 +15264,7 @@
     },
     {
       "file": "packages/@ember/application/instance.ts",
-      "line": 393,
+      "line": 394,
       "description": "If present, overrides the router's `location` property with this\nvalue. This is useful for environments where trying to modify the\nURL would be inappropriate.",
       "itemtype": "property",
       "name": "location",
@@ -15273,7 +15278,7 @@
     },
     {
       "file": "packages/@ember/application/instance.ts",
-      "line": 405,
+      "line": 406,
       "description": "Disable rendering completely.\n\nWhen this flag is set to `false`, it will disable the entire rendering\npipeline. Essentially, this puts the app into \"routing-only\" mode. No\ntemplates will be rendered, and no Components will be created.",
       "itemtype": "property",
       "name": "shouldRender",
@@ -15287,7 +15292,7 @@
     },
     {
       "file": "packages/@ember/application/instance.ts",
-      "line": 419,
+      "line": 420,
       "description": "If present, render into the given `Document` object instead of the\nglobal `window.document` object.\n\nIn practice, this is only useful in non-browser environment or in\nnon-interactive mode, because Ember's `jQuery` dependency is\nimplicitly bound to the current document, causing event delegation\nto not work properly when the app is rendered into a foreign\ndocument object (such as an iframe's `contentDocument`).\n\nIn non-browser mode, this could be a \"`Document`-like\" object as\nEmber only interact with a small subset of the DOM API in non-\ninteractive mode. While the exact requirements have not yet been\nformalized, the `SimpleDOM` library's implementation is known to\nwork.",
       "itemtype": "property",
       "name": "document",
@@ -15301,7 +15306,7 @@
     },
     {
       "file": "packages/@ember/application/instance.ts",
-      "line": 442,
+      "line": 443,
       "description": "If present, overrides the application's `rootElement` property on\nthe instance. This is useful for testing environment, where you\nmight want to append the root view to a fixture area.\n\nIn non-browser mode, because Ember does not have access to jQuery,\nthis options must be specified as a DOM `Element` object instead of\na selector string.\n\nSee the documentation on `Application`'s `rootElement` for\ndetails.",
       "itemtype": "property",
       "name": "rootElement",
@@ -15362,14 +15367,15 @@
       "module": "@ember/component/template-only"
     },
     {
-      "file": "packages/@ember/controller/lib/controller_mixin.d.ts",
-      "line": 11,
+      "file": "packages/@ember/controller/lib/controller_mixin.ts",
+      "line": 24,
       "class": "Ember.ControllerMixin",
-      "module": "@ember/component/template-only"
+      "module": "ember",
+      "namespace": "Ember"
     },
     {
-      "file": "packages/@ember/controller/lib/controller_mixin.js",
-      "line": 21,
+      "file": "packages/@ember/controller/lib/controller_mixin.ts",
+      "line": 43,
       "description": "The object to which actions from the view should be sent.\n\nFor example, when a Handlebars template uses the `{{action}}` helper,\nit will attempt to send the action to the view's controller's `target`.\n\nBy default, the value of the target property is set to the router, and\nis injected when a controller is instantiated. This injection is applied\nas part of the application's initialization process. In most cases the\n`target` property will automatically be set to the logical consumer of\nactions for the controller.",
       "itemtype": "property",
       "name": "target",
@@ -15381,8 +15387,8 @@
       "namespace": "Ember"
     },
     {
-      "file": "packages/@ember/controller/lib/controller_mixin.js",
-      "line": 41,
+      "file": "packages/@ember/controller/lib/controller_mixin.ts",
+      "line": 63,
       "description": "The controller's current model. When retrieving or modifying a controller's\nmodel, this property should be used instead of the `content` property.",
       "itemtype": "property",
       "name": "model",
@@ -15438,7 +15444,7 @@
     },
     {
       "file": "packages/@ember/debug/lib/deprecate.ts",
-      "line": 36,
+      "line": 37,
       "description": "Allows for runtime registration of handler functions that override the default deprecation behavior.\nDeprecations are invoked by calls to [@ember/debug/deprecate](/ember/release/classes/@ember%2Fdebug/methods/deprecate?anchor=deprecate).\nThe following example demonstrates its usage by registering a handler that throws an error if the\nmessage contains the word \"should\", otherwise defers to the default handler.\n\n```javascript\nimport { registerDeprecationHandler } from '@ember/debug';\n\nregisterDeprecationHandler((message, options, next) => {\n  if (message.indexOf('should') !== -1) {\n    throw new Error(`Deprecation message with should: ${message}`);\n  } else {\n    // defer to whatever handler was registered before this one\n    next(message, options);\n  }\n});\n```\n\nThe handler function takes the following arguments:\n\n<ul>\n  <li> <code>message</code> - The message received from the deprecation call.</li>\n  <li> <code>options</code> - An object passed in with the deprecation call containing additional information including:</li>\n    <ul>\n      <li> <code>id</code> - An id of the deprecation in the form of <code>package-name.specific-deprecation</code>.</li>\n      <li> <code>until</code> - The Ember version number the feature and deprecation will be removed in.</li>\n    </ul>\n  <li> <code>next</code> - A function that calls into the previously registered handler.</li>\n</ul>",
       "access": "public",
       "tagname": "",
@@ -15458,7 +15464,7 @@
     },
     {
       "file": "packages/@ember/debug/lib/deprecate.ts",
-      "line": 181,
+      "line": 182,
       "description": "Display a deprecation warning with the provided message and a stack trace\n(Chrome and Firefox only).\n\n* In a production build, this method is defined as an empty function (NOP).\nUses of this method in Ember itself are stripped from the ember.prod.js build.",
       "itemtype": "method",
       "name": "deprecate",
@@ -15516,7 +15522,7 @@
     },
     {
       "file": "packages/@ember/debug/lib/warn.ts",
-      "line": 23,
+      "line": 24,
       "description": "Allows for runtime registration of handler functions that override the default warning behavior.\nWarnings are invoked by calls made to [@ember/debug/warn](/ember/release/classes/@ember%2Fdebug/methods/warn?anchor=warn).\nThe following example demonstrates its usage by registering a handler that does nothing overriding Ember's\ndefault warning behavior.\n\n```javascript\nimport { registerWarnHandler } from '@ember/debug';\n\n// next is not called, so no warnings get the default behavior\nregisterWarnHandler(() => {});\n```\n\nThe handler function takes the following arguments:\n\n<ul>\n  <li> <code>message</code> - The message received from the warn call. </li>\n  <li> <code>options</code> - An object passed in with the warn call containing additional information including:</li>\n    <ul>\n      <li> <code>id</code> - An id of the warning in the form of <code>package-name.specific-warning</code>.</li>\n    </ul>\n  <li> <code>next</code> - A function that calls into the previously registered handler.</li>\n</ul>",
       "access": "public",
       "tagname": "",
@@ -15536,7 +15542,7 @@
     },
     {
       "file": "packages/@ember/debug/lib/warn.ts",
-      "line": 70,
+      "line": 71,
       "description": "Display a warning with the provided message.\n\n* In a production build, this method is defined as an empty function (NOP).\nUses of this method in Ember itself are stripped from the ember.prod.js build.\n\n```javascript\nimport { warn } from '@ember/debug';\nimport tomsterCount from './tomster-counter'; // a module in my project\n\n// Log a warning if we have more than 3 tomsters\nwarn('Too many tomsters!', tomsterCount <= 3, {\n  id: 'ember-debug.too-many-tomsters'\n});\n```",
       "itemtype": "method",
       "name": "warn",
@@ -15566,7 +15572,7 @@
     },
     {
       "file": "packages/@ember/debug/index.ts",
-      "line": 134,
+      "line": 136,
       "description": "Verify that a certain expectation is met, or throw a exception otherwise.\n\nThis is useful for communicating assumptions in the code to other human\nreaders as well as catching bugs that accidentally violates these\nexpectations.\n\nAssertions are removed from production builds, so they can be freely added\nfor documentation and debugging purposes without worries of incuring any\nperformance penalty. However, because of that, they should not be used for\nchecks that could reasonably fail during normal usage. Furthermore, care\nshould be taken to avoid accidentally relying on side-effects produced from\nevaluating the condition itself, since the code will not run in production.\n\n```javascript\nimport { assert } from '@ember/debug';\n\n// Test for truthiness\nassert('Must pass a string', typeof str === 'string');\n\n// Fail unconditionally\nassert('This code path should never be run');\n```",
       "itemtype": "method",
       "name": "assert",
@@ -15591,7 +15597,7 @@
     },
     {
       "file": "packages/@ember/debug/index.ts",
-      "line": 174,
+      "line": 176,
       "description": "Display a debug notice.\n\nCalls to this function are not invoked in production builds.\n\n```javascript\nimport { debug } from '@ember/debug';\n\ndebug('I\\'m a debug notice!');\n```",
       "itemtype": "method",
       "name": "debug",
@@ -15610,7 +15616,7 @@
     },
     {
       "file": "packages/@ember/debug/index.ts",
-      "line": 201,
+      "line": 203,
       "description": "Display an info notice.\n\nCalls to this function are removed from production builds, so they can be\nfreely added for documentation and debugging purposes without worries of\nincuring any performance penalty.",
       "itemtype": "method",
       "name": "info",
@@ -15621,7 +15627,7 @@
     },
     {
       "file": "packages/@ember/debug/index.ts",
-      "line": 220,
+      "line": 222,
       "description": "Alias an old, deprecated method with its new counterpart.\n\nDisplay a deprecation warning with the provided message and a stack trace\n(Chrome and Firefox only) when the assigned method is called.\n\nCalls to this function are removed from production builds, so they can be\nfreely added for documentation and debugging purposes without worries of\nincuring any performance penalty.\n\n```javascript\nimport { deprecateFunc } from '@ember/debug';\n\nEmber.oldMethod = deprecateFunc('Please use the new, updated method', options, Ember.newMethod);\n```",
       "itemtype": "method",
       "name": "deprecateFunc",
@@ -15655,7 +15661,7 @@
     },
     {
       "file": "packages/@ember/debug/index.ts",
-      "line": 265,
+      "line": 267,
       "description": "Run a function meant for debugging.\n\nCalls to this function are removed from production builds, so they can be\nfreely added for documentation and debugging purposes without worries of\nincuring any performance penalty.\n\n```javascript\nimport Component from '@ember/component';\nimport { runInDebug } from '@ember/debug';\n\nrunInDebug(() => {\n  Component.reopen({\n    didInsertElement() {\n      console.log(\"I'm happy\");\n    }\n  });\n});\n```",
       "itemtype": "method",
       "name": "runInDebug",
@@ -15886,7 +15892,7 @@
     },
     {
       "file": "packages/@ember/engine/index.ts",
-      "line": 61,
+      "line": 62,
       "description": "The goal of initializers should be to register dependencies and injections.\nThis phase runs once. Because these initializers may load code, they are\nallowed to defer application readiness and advance it. If you need to access\nthe container or store you should use an InstanceInitializer that will be run\nafter all initializers and therefore after all code is loaded and the app is\nready.\n\nInitializer receives an object which has the following attributes:\n`name`, `before`, `after`, `initialize`. The only required attribute is\n`initialize`, all others are optional.\n\n* `name` allows you to specify under which name the initializer is registered.\nThis must be a unique name, as trying to register two initializers with the\nsame name will result in an error.\n\n```app/initializer/named-initializer.js\nimport { debug } from '@ember/debug';\n\nexport function initialize() {\n  debug('Running namedInitializer!');\n}\n\nexport default {\n  name: 'named-initializer',\n  initialize\n};\n```\n\n* `before` and `after` are used to ensure that this initializer is ran prior\nor after the one identified by the value. This value can be a single string\nor an array of strings, referencing the `name` of other initializers.\n\nAn example of ordering initializers, we create an initializer named `first`:\n\n```app/initializer/first.js\nimport { debug } from '@ember/debug';\n\nexport function initialize() {\n  debug('First initializer!');\n}\n\nexport default {\n  name: 'first',\n  initialize\n};\n```\n\n```bash\n// DEBUG: First initializer!\n```\n\nWe add another initializer named `second`, specifying that it should run\nafter the initializer named `first`:\n\n```app/initializer/second.js\nimport { debug } from '@ember/debug';\n\nexport function initialize() {\n  debug('Second initializer!');\n}\n\nexport default {\n  name: 'second',\n  after: 'first',\n  initialize\n};\n```\n\n```\n// DEBUG: First initializer!\n// DEBUG: Second initializer!\n```\n\nAfterwards we add a further initializer named `pre`, this time specifying\nthat it should run before the initializer named `first`:\n\n```app/initializer/pre.js\nimport { debug } from '@ember/debug';\n\nexport function initialize() {\n  debug('Pre initializer!');\n}\n\nexport default {\n  name: 'pre',\n  before: 'first',\n  initialize\n};\n```\n\n```bash\n// DEBUG: Pre initializer!\n// DEBUG: First initializer!\n// DEBUG: Second initializer!\n```\n\nFinally we add an initializer named `post`, specifying it should run after\nboth the `first` and the `second` initializers:\n\n```app/initializer/post.js\nimport { debug } from '@ember/debug';\n\nexport function initialize() {\n  debug('Post initializer!');\n}\n\nexport default {\n  name: 'post',\n  after: ['first', 'second'],\n  initialize\n};\n```\n\n```bash\n// DEBUG: Pre initializer!\n// DEBUG: First initializer!\n// DEBUG: Second initializer!\n// DEBUG: Post initializer!\n```\n\n* `initialize` is a callback function that receives one argument,\n  `application`, on which you can operate.\n\nExample of using `application` to register an adapter:\n\n```app/initializer/api-adapter.js\nimport ApiAdapter from '../utils/api-adapter';\n\nexport function initialize(application) {\n  application.register('api-adapter:main', ApiAdapter);\n}\n\nexport default {\n  name: 'post',\n  after: ['first', 'second'],\n  initialize\n};\n```",
       "itemtype": "method",
       "name": "initializer",
@@ -15904,7 +15910,7 @@
     },
     {
       "file": "packages/@ember/engine/index.ts",
-      "line": 208,
+      "line": 209,
       "description": "Instance initializers run after all initializers have run. Because\ninstance initializers run after the app is fully set up. We have access\nto the store, container, and other items. However, these initializers run\nafter code has loaded and are not allowed to defer readiness.\n\nInstance initializer receives an object which has the following attributes:\n`name`, `before`, `after`, `initialize`. The only required attribute is\n`initialize`, all others are optional.\n\n* `name` allows you to specify under which name the instanceInitializer is\nregistered. This must be a unique name, as trying to register two\ninstanceInitializer with the same name will result in an error.\n\n```app/initializer/named-instance-initializer.js\nimport { debug } from '@ember/debug';\n\nexport function initialize() {\n  debug('Running named-instance-initializer!');\n}\n\nexport default {\n  name: 'named-instance-initializer',\n  initialize\n};\n```\n\n* `before` and `after` are used to ensure that this initializer is ran prior\nor after the one identified by the value. This value can be a single string\nor an array of strings, referencing the `name` of other initializers.\n\n* See Application.initializer for discussion on the usage of before\nand after.\n\nExample instanceInitializer to preload data into the store.\n\n```app/initializer/preload-data.js\n\nexport function initialize(application) {\n    var userConfig, userConfigEncoded, store;\n    // We have a HTML escaped JSON representation of the user's basic\n    // configuration generated server side and stored in the DOM of the main\n    // index.html file. This allows the app to have access to a set of data\n    // without making any additional remote calls. Good for basic data that is\n    // needed for immediate rendering of the page. Keep in mind, this data,\n    // like all local models and data can be manipulated by the user, so it\n    // should not be relied upon for security or authorization.\n\n    // Grab the encoded data from the meta tag\n    userConfigEncoded = document.querySelector('head meta[name=app-user-config]').attr('content');\n\n    // Unescape the text, then parse the resulting JSON into a real object\n    userConfig = JSON.parse(unescape(userConfigEncoded));\n\n    // Lookup the store\n    store = application.lookup('service:store');\n\n    // Push the encoded JSON into the store\n    store.pushPayload(userConfig);\n}\n\nexport default {\n  name: 'named-instance-initializer',\n  initialize\n};\n```",
       "itemtype": "method",
       "name": "instanceInitializer",
@@ -15921,7 +15927,7 @@
     },
     {
       "file": "packages/@ember/engine/index.ts",
-      "line": 284,
+      "line": 285,
       "description": "This creates a registry with the default Ember naming conventions.\n\nIt also configures the registry:\n\n* registered views are created every time they are looked up (they are\n  not singletons)\n* registered templates are not factories; the registered value is\n  returned directly.\n* the router receives the application as its `namespace` property\n* all controllers receive the router as their `target` and `controllers`\n  properties\n* all controllers receive the application as their `namespace` property\n* the application view receives the application controller as its\n  `controller` property\n* the application view receives the application template as its\n  `defaultTemplate` property",
       "itemtype": "method",
       "name": "buildRegistry",
@@ -15944,7 +15950,7 @@
     },
     {
       "file": "packages/@ember/engine/index.ts",
-      "line": 324,
+      "line": 325,
       "description": "Set this to provide an alternate class to `DefaultResolver`",
       "itemtype": "property",
       "name": "resolver",
@@ -15955,7 +15961,7 @@
     },
     {
       "file": "packages/@ember/engine/index.ts",
-      "line": 337,
+      "line": 338,
       "description": "A private flag indicating whether an engine's initializers have run yet.",
       "access": "private",
       "tagname": "",
@@ -15966,7 +15972,7 @@
     },
     {
       "file": "packages/@ember/engine/index.ts",
-      "line": 345,
+      "line": 346,
       "description": "Ensure that initializers are run once, and only once, per engine.",
       "access": "private",
       "tagname": "",
@@ -15977,7 +15983,7 @@
     },
     {
       "file": "packages/@ember/engine/index.ts",
-      "line": 358,
+      "line": 359,
       "description": "Create an EngineInstance for this engine.",
       "access": "public",
       "tagname": "",
@@ -15992,7 +15998,7 @@
     },
     {
       "file": "packages/@ember/engine/index.ts",
-      "line": 370,
+      "line": 371,
       "description": "Build and configure the registry for the current engine.",
       "access": "private",
       "tagname": "",
@@ -16007,7 +16013,7 @@
     },
     {
       "file": "packages/@ember/engine/index.ts",
-      "line": 383,
+      "line": 384,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -16017,7 +16023,7 @@
     },
     {
       "file": "packages/@ember/engine/index.ts",
-      "line": 391,
+      "line": 392,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -16027,7 +16033,7 @@
     },
     {
       "file": "packages/@ember/engine/index.ts",
-      "line": 399,
+      "line": 400,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -16037,7 +16043,7 @@
     },
     {
       "file": "packages/@ember/engine/index.ts",
-      "line": 413,
+      "line": 414,
       "access": "private",
       "tagname": "",
       "since": "1.12.0",
@@ -16048,7 +16054,7 @@
     },
     {
       "file": "packages/@ember/engine/index.ts",
-      "line": 447,
+      "line": 448,
       "description": "This function defines the default lookup rules for container lookups:\n\n* templates are looked up on `Ember.TEMPLATES`\n* other names are looked up on the application after classifying the name.\n  For example, `controller:post` looks up `App.PostController` by default.\n* if the default lookup fails, look for registered classes on the container\n\nThis allows the application to register default injections in the container\nthat could be overridden by the normal naming convention.",
       "access": "private",
       "tagname": "",
@@ -16374,8 +16380,8 @@
       "module": "@ember/instrumentation"
     },
     {
-      "file": "packages/@ember/object/lib/computed/computed_macros.js",
-      "line": 63,
+      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
+      "line": 67,
       "description": "A computed property macro that returns true if the value of the dependent\nproperty is null, an empty string, empty array, or empty function.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { empty } from '@ember/object/computed';\n\nclass ToDoList {\n  constructor(todos) {\n    set(this, 'todos', todos);\n  }\n\n  @empty('todos') isDone;\n}\n\nlet todoList = new ToDoList(\n  ['Unit Test', 'Documentation', 'Release']\n);\n\ntodoList.isDone; // false\nset(todoList, 'todos', []);\ntodoList.isDone; // true\n```",
       "since": "1.6.0",
       "itemtype": "method",
@@ -16398,8 +16404,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/computed_macros.js",
-      "line": 112,
+      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
+      "line": 116,
       "description": "A computed property that returns true if the value of the dependent property\nis NOT null, an empty string, empty array, or empty function.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { notEmpty } from '@ember/object/computed';\n\nclass Hamster {\n  constructor(backpack) {\n    set(this, 'backpack', backpack);\n  }\n\n  @notEmpty('backpack') hasStuff\n}\n\nlet hamster = new Hamster(\n  ['Food', 'Sleeping Bag', 'Tent']\n);\n\nhamster.hasStuff; // true\nset(hamster, 'backpack', []);\nhamster.hasStuff; // false\n```",
       "itemtype": "method",
       "name": "notEmpty",
@@ -16421,8 +16427,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/computed_macros.js",
-      "line": 158,
+      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
+      "line": 162,
       "description": "A computed property that returns true if the value of the dependent property\nis null or undefined. This avoids errors from JSLint complaining about use of\n==, which can be technically confusing.\n\n```javascript\nimport { set } from '@ember/object';\nimport { none } from '@ember/object/computed';\n\nclass Hamster {\n  @none('food') isHungry;\n}\n\nlet hamster = new Hamster();\n\nhamster.isHungry; // true\n\nset(hamster, 'food', 'Banana');\nhamster.isHungry; // false\n\nset(hamster, 'food', null);\nhamster.isHungry; // true\n```",
       "itemtype": "method",
       "name": "none",
@@ -16444,8 +16450,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/computed_macros.js",
-      "line": 201,
+      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
+      "line": 205,
       "description": "A computed property that returns the inverse boolean value of the original\nvalue for the dependent property.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { not } from '@ember/object/computed';\n\nclass User {\n  loggedIn = false;\n\n  @not('loggedIn') isAnonymous;\n}\n\nlet user = new User();\n\nuser.isAnonymous; // true\nset(user, 'loggedIn', true);\nuser.isAnonymous; // false\n```",
       "itemtype": "method",
       "name": "not",
@@ -16467,8 +16473,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/computed_macros.js",
-      "line": 243,
+      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
+      "line": 247,
       "description": "A computed property that converts the provided dependent property into a\nboolean value.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { bool } from '@ember/object/computed';\n\n\nclass Hamster {\n  @bool('numBananas') hasBananas\n}\n\nlet hamster = new Hamster();\n\nhamster.hasBananas; // false\n\nset(hamster, 'numBananas', 0);\nhamster.hasBananas; // false\n\nset(hamster, 'numBananas', 1);\nhamster.hasBananas; // true\n\nset(hamster, 'numBananas', null);\nhamster.hasBananas; // false\n```",
       "itemtype": "method",
       "name": "bool",
@@ -16490,8 +16496,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/computed_macros.js",
-      "line": 291,
+      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
+      "line": 295,
       "description": "A computed property which matches the original value for the dependent\nproperty against a given RegExp, returning `true` if the value matches the\nRegExp and `false` if it does not.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { match } from '@ember/object/computed';\n\nclass User {\n  @match('email', /^.+@.+\\..+$/) hasValidEmail;\n}\n\nlet user = new User();\n\nuser.hasValidEmail; // false\n\nset(user, 'email', '');\nuser.hasValidEmail; // false\n\nset(user, 'email', 'ember_hamster@example.com');\nuser.hasValidEmail; // true\n```",
       "itemtype": "method",
       "name": "match",
@@ -16518,8 +16524,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/computed_macros.js",
-      "line": 338,
+      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
+      "line": 342,
       "description": "A computed property that returns true if the provided dependent property is\nequal to the given value.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { equal } from '@ember/object/computed';\n\nclass Hamster {\n  @equal('percentCarrotsEaten', 100) satisfied;\n}\n\nlet hamster = new Hamster();\n\nhamster.satisfied; // false\n\nset(hamster, 'percentCarrotsEaten', 100);\nhamster.satisfied; // true\n\nset(hamster, 'percentCarrotsEaten', 50);\nhamster.satisfied; // false\n```",
       "itemtype": "method",
       "name": "equal",
@@ -16546,8 +16552,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/computed_macros.js",
-      "line": 383,
+      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
+      "line": 387,
       "description": "A computed property that returns true if the provided dependent property is\ngreater than the provided value.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { gt } from '@ember/object/computed';\n\nclass Hamster {\n  @gt('numBananas', 10) hasTooManyBananas;\n}\n\nlet hamster = new Hamster();\n\nhamster.hasTooManyBananas; // false\n\nset(hamster, 'numBananas', 3);\nhamster.hasTooManyBananas; // false\n\nset(hamster, 'numBananas', 11);\nhamster.hasTooManyBananas; // true\n```",
       "itemtype": "method",
       "name": "gt",
@@ -16574,8 +16580,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/computed_macros.js",
-      "line": 428,
+      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
+      "line": 432,
       "description": "A computed property that returns true if the provided dependent property is\ngreater than or equal to the provided value.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { gte } from '@ember/object/computed';\n\nclass Hamster {\n  @gte('numBananas', 10) hasTooManyBananas;\n}\n\nlet hamster = new Hamster();\n\nhamster.hasTooManyBananas; // false\n\nset(hamster, 'numBananas', 3);\nhamster.hasTooManyBananas; // false\n\nset(hamster, 'numBananas', 10);\nhamster.hasTooManyBananas; // true\n```",
       "itemtype": "method",
       "name": "gte",
@@ -16602,8 +16608,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/computed_macros.js",
-      "line": 473,
+      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
+      "line": 477,
       "description": "A computed property that returns true if the provided dependent property is\nless than the provided value.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { lt } from '@ember/object/computed';\n\nclass Hamster {\n  @lt('numBananas', 3) needsMoreBananas;\n}\n\nlet hamster = new Hamster();\n\nhamster.needsMoreBananas; // true\n\nset(hamster, 'numBananas', 3);\nhamster.needsMoreBananas; // false\n\nset(hamster, 'numBananas', 2);\nhamster.needsMoreBananas; // true\n```",
       "itemtype": "method",
       "name": "lt",
@@ -16630,8 +16636,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/computed_macros.js",
-      "line": 518,
+      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
+      "line": 522,
       "description": "A computed property that returns true if the provided dependent property is\nless than or equal to the provided value.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { lte } from '@ember/object/computed';\n\nclass Hamster {\n  @lte('numBananas', 3) needsMoreBananas;\n}\n\nlet hamster = new Hamster();\n\nhamster.needsMoreBananas; // true\n\nset(hamster, 'numBananas', 5);\nhamster.needsMoreBananas; // false\n\nset(hamster, 'numBananas', 3);\nhamster.needsMoreBananas; // true\n```",
       "itemtype": "method",
       "name": "lte",
@@ -16658,8 +16664,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/computed_macros.js",
-      "line": 563,
+      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
+      "line": 567,
       "description": "A computed property that performs a logical `and` on the original values for\nthe provided dependent properties.\n\nYou may pass in more than two properties and even use property brace\nexpansion.  The computed property will return the first falsy value or last\ntruthy value just like JavaScript's `&&` operator.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { and } from '@ember/object/computed';\n\nclass Hamster {\n  @and('hasTent', 'hasBackpack') readyForCamp;\n  @and('hasWalkingStick', 'hasBackpack') readyForHike;\n}\n\nlet tomster = new Hamster();\n\ntomster.readyForCamp; // false\n\nset(tomster, 'hasTent', true);\ntomster.readyForCamp; // false\n\nset(tomster, 'hasBackpack', true);\ntomster.readyForCamp; // true\n\nset(tomster, 'hasBackpack', 'Yes');\ntomster.readyForCamp; // 'Yes'\n\nset(tomster, 'hasWalkingStick', null);\ntomster.readyForHike; // null\n```",
       "itemtype": "method",
       "name": "and",
@@ -16682,8 +16688,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/computed_macros.js",
-      "line": 609,
+      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
+      "line": 613,
       "description": "A computed property which performs a logical `or` on the original values for\nthe provided dependent properties.\n\nYou may pass in more than two properties and even use property brace\nexpansion.  The computed property will return the first truthy value or last\nfalsy value just like JavaScript's `||` operator.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { or } from '@ember/object/computed';\n\nclass Hamster {\n  @or('hasJacket', 'hasUmbrella') readyForRain;\n  @or('hasSunscreen', 'hasUmbrella') readyForBeach;\n}\n\nlet tomster = new Hamster();\n\ntomster.readyForRain; // undefined\n\nset(tomster, 'hasUmbrella', true);\ntomster.readyForRain; // true\n\nset(tomster, 'hasJacket', 'Yes');\ntomster.readyForRain; // 'Yes'\n\nset(tomster, 'hasSunscreen', 'Check');\ntomster.readyForBeach; // 'Check'\n```",
       "itemtype": "method",
       "name": "or",
@@ -16706,8 +16712,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/computed_macros.js",
-      "line": 652,
+      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
+      "line": 656,
       "description": "Creates a new property that is an alias for another property on an object.\nCalls to `get` or `set` this property behave as though they were called on the\noriginal property.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { alias } from '@ember/object/computed';\n\nclass Person {\n  name = 'Alex Matchneer';\n\n  @alias('name') nomen;\n}\n\nlet alex = new Person();\n\nalex.nomen; // 'Alex Matchneer'\nalex.name;  // 'Alex Matchneer'\n\nset(alex, 'nomen', '@machty');\nalex.name;  // '@machty'\n```",
       "itemtype": "method",
       "name": "alias",
@@ -16729,8 +16735,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/computed_macros.js",
-      "line": 687,
+      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
+      "line": 691,
       "description": "Where the `alias` computed macro aliases `get` and `set`, and allows for\nbidirectional data flow, the `oneWay` computed macro only provides an aliased\n`get`. The `set` will not mutate the upstream property, rather causes the\ncurrent property to become the value set. This causes the downstream property\nto permanently diverge from the upstream property.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { oneWay }from '@ember/object/computed';\n\nclass User {\n  constructor(firstName, lastName) {\n    set(this, 'firstName', firstName);\n    set(this, 'lastName', lastName);\n  }\n\n  @oneWay('firstName') nickName;\n}\n\nlet teddy = new User('Teddy', 'Zeenny');\n\nteddy.nickName; // 'Teddy'\n\nset(teddy, 'nickName', 'TeddyBear');\nteddy.firstName; // 'Teddy'\nteddy.nickName; // 'TeddyBear'\n```",
       "itemtype": "method",
       "name": "oneWay",
@@ -16752,8 +16758,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/computed_macros.js",
-      "line": 735,
+      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
+      "line": 739,
       "description": "This is a more semantically meaningful alias of the `oneWay` computed macro,\nwhose name is somewhat ambiguous as to which direction the data flows.",
       "itemtype": "method",
       "name": "reads",
@@ -16775,8 +16781,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/computed_macros.js",
-      "line": 748,
+      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
+      "line": 752,
       "description": "Where `oneWay` computed macro provides oneWay bindings, the `readOnly`\ncomputed macro provides a readOnly one way binding. Very often when using\nthe `oneWay` macro one does not also want changes to propagate back up, as\nthey will replace the value.\n\nThis prevents the reverse flow, and also throws an exception when it occurs.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { readOnly } from '@ember/object/computed';\n\nclass User {\n  constructor(firstName, lastName) {\n    set(this, 'firstName', firstName);\n    set(this, 'lastName', lastName);\n  }\n\n  @readOnly('firstName') nickName;\n});\n\nlet teddy = new User('Teddy', 'Zeenny');\n\nteddy.nickName; // 'Teddy'\n\nset(teddy, 'nickName', 'TeddyBear'); // throws Exception\n// throw new EmberError('Cannot Set: nickName on: <User:ember27288>' );`\n\nteddy.firstName; // 'Teddy'\n```",
       "itemtype": "method",
       "name": "readOnly",
@@ -16799,8 +16805,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/computed_macros.js",
-      "line": 799,
+      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
+      "line": 803,
       "description": "Creates a new property that is an alias for another property on an object.\nCalls to `get` or `set` this property behave as though they were called on the\noriginal property, but also print a deprecation warning.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { deprecatingAlias } from '@ember/object/computed';\n\nclass Hamster {\n  @deprecatingAlias('cavendishCount', {\n    id: 'hamster.deprecate-banana',\n    until: '3.0.0'\n  })\n  bananaCount;\n}\n\nlet hamster = new Hamster();\n\nset(hamster, 'bananaCount', 5); // Prints a deprecation warning.\nhamster.cavendishCount; // 5\n```",
       "itemtype": "method",
       "name": "deprecatingAlias",
@@ -16828,8 +16834,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.js",
-      "line": 56,
+      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.ts",
+      "line": 75,
       "description": "A computed property that returns the sum of the values in the dependent array.\n\nExample:\n\n```javascript\nimport { sum } from '@ember/object/computed';\n\nclass Invoice {\n  lineItems = [1.00, 2.50, 9.99];\n\n  @sum('lineItems') total;\n}\n\nlet invoice = new Invoice();\n\ninvoice.total; // 13.49\n```",
       "itemtype": "method",
       "name": "sum",
@@ -16852,8 +16858,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.js",
-      "line": 93,
+      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.ts",
+      "line": 112,
       "description": "A computed property that calculates the maximum value in the dependent array.\nThis will return `-Infinity` when the dependent array is empty.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { mapBy, max } from '@ember/object/computed';\n\nclass Person {\n  children = [];\n\n  @mapBy('children', 'age') childAges;\n  @max('childAges') maxChildAge;\n}\n\nlet lordByron = new Person();\n\nlordByron.maxChildAge; // -Infinity\n\nset(lordByron, 'children', [\n  {\n    name: 'Augusta Ada Byron',\n    age: 7\n  }\n]);\nlordByron.maxChildAge; // 7\n\nset(lordByron, 'children', [\n  ...lordByron.children,\n  {\n    name: 'Allegra Byron',\n    age: 5\n  }, {\n    name: 'Elizabeth Medora Leigh',\n    age: 8\n  }\n]);\nlordByron.maxChildAge; // 8\n```\n\nIf the types of the arguments are not numbers, they will be converted to\nnumbers and the type of the return value will always be `Number`. For example,\nthe max of a list of Date objects will be the highest timestamp as a `Number`.\nThis behavior is consistent with `Math.max`.",
       "itemtype": "method",
       "name": "max",
@@ -16875,8 +16881,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.js",
-      "line": 157,
+      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.ts",
+      "line": 176,
       "description": "A computed property that calculates the minimum value in the dependent array.\nThis will return `Infinity` when the dependent array is empty.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { mapBy, min } from '@ember/object/computed';\n\nclass Person {\n  children = [];\n\n  @mapBy('children', 'age') childAges;\n  @min('childAges') minChildAge;\n}\n\nlet lordByron = Person.create({ children: [] });\n\nlordByron.minChildAge; // Infinity\n\nset(lordByron, 'children', [\n  {\n    name: 'Augusta Ada Byron',\n    age: 7\n  }\n]);\nlordByron.minChildAge; // 7\n\nset(lordByron, 'children', [\n  ...lordByron.children,\n  {\n    name: 'Allegra Byron',\n    age: 5\n  }, {\n    name: 'Elizabeth Medora Leigh',\n    age: 8\n  }\n]);\nlordByron.minChildAge; // 5\n```\n\nIf the types of the arguments are not numbers, they will be converted to\nnumbers and the type of the return value will always be `Number`. For example,\nthe min of a list of Date objects will be the lowest timestamp as a `Number`.\nThis behavior is consistent with `Math.min`.",
       "itemtype": "method",
       "name": "min",
@@ -16898,8 +16904,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.js",
-      "line": 220,
+      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.ts",
+      "line": 239,
       "description": "Returns an array mapped via the callback\n\nThe callback method you provide should have the following signature:\n- `item` is the current item in the iteration.\n- `index` is the integer index of the current item in the iteration.\n\n```javascript\nfunction mapCallback(item, index);\n```\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { map } from '@ember/object/computed';\n\nclass Hamster {\n  constructor(chores) {\n    set(this, 'chores', chores);\n  }\n\n  @map('chores', function(chore, index) {\n    return `${chore.toUpperCase()}!`;\n  })\n  excitingChores;\n});\n\nlet hamster = new Hamster(['clean', 'write more unit tests']);\n\nhamster.excitingChores; // ['CLEAN!', 'WRITE MORE UNIT TESTS!']\n```\n\nYou can optionally pass an array of additional dependent keys as the second\nparameter to the macro, if your map function relies on any external values:\n\n```javascript\nimport { set } from '@ember/object';\nimport { map } from '@ember/object/computed';\n\nclass Hamster {\n  shouldUpperCase = false;\n\n  constructor(chores) {\n    set(this, 'chores', chores);\n  }\n\n  @map('chores', ['shouldUpperCase'], function(chore, index) {\n    if (this.shouldUpperCase) {\n      return `${chore.toUpperCase()}!`;\n    } else {\n      return `${chore}!`;\n    }\n  })\n  excitingChores;\n}\n\nlet hamster = new Hamster(['clean', 'write more unit tests']);\n\nhamster.excitingChores; // ['clean!', 'write more unit tests!']\n\nset(hamster, 'shouldUpperCase', true);\nhamster.excitingChores; // ['CLEAN!', 'WRITE MORE UNIT TESTS!']\n```",
       "itemtype": "method",
       "name": "map",
@@ -16932,8 +16938,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.js",
-      "line": 321,
+      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.ts",
+      "line": 363,
       "description": "Returns an array mapped to the specified key.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { mapBy } from '@ember/object/computed';\n\nclass Person {\n  children = [];\n\n  @mapBy('children', 'age') childAges;\n}\n\nlet lordByron = new Person();\n\nlordByron.childAges; // []\n\nset(lordByron, 'children', [\n  {\n    name: 'Augusta Ada Byron',\n    age: 7\n  }\n]);\nlordByron.childAges; // [7]\n\nset(lordByron, 'children', [\n  ...lordByron.children,\n  {\n    name: 'Allegra Byron',\n    age: 5\n  }, {\n    name: 'Elizabeth Medora Leigh',\n    age: 8\n  }\n]);\nlordByron.childAges; // [7, 5, 8]\n```",
       "itemtype": "method",
       "name": "mapBy",
@@ -16960,8 +16966,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.js",
-      "line": 388,
+      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.ts",
+      "line": 430,
       "description": "Filters the array by the callback.\n\nThe callback method you provide should have the following signature:\n- `item` is the current item in the iteration.\n- `index` is the integer index of the current item in the iteration.\n- `array` is the dependant array itself.\n\n```javascript\nfunction filterCallback(item, index, array);\n```\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { filter } from '@ember/object/computed';\n\nclass Hamster {\n  constructor(chores) {\n    set(this, 'chores', chores);\n  }\n\n  @filter('chores', function(chore, index, array) {\n    return !chore.done;\n  })\n  remainingChores;\n}\n\nlet hamster = Hamster.create([\n  { name: 'cook', done: true },\n  { name: 'clean', done: true },\n  { name: 'write more unit tests', done: false }\n]);\n\nhamster.remainingChores; // [{name: 'write more unit tests', done: false}]\n```\n\nYou can also use `@each.property` in your dependent key, the callback will\nstill use the underlying array:\n\n```javascript\nimport { set } from '@ember/object';\nimport { filter } from '@ember/object/computed';\n\nclass Hamster {\n  constructor(chores) {\n    set(this, 'chores', chores);\n  }\n\n  @filter('chores.@each.done', function(chore, index, array) {\n    return !chore.done;\n  })\n  remainingChores;\n}\n\nlet hamster = new Hamster([\n  { name: 'cook', done: true },\n  { name: 'clean', done: true },\n  { name: 'write more unit tests', done: false }\n]);\nhamster.remainingChores; // [{name: 'write more unit tests', done: false}]\n\nset(hamster.chores[2], 'done', true);\nhamster.remainingChores; // []\n```\n\nFinally, you can optionally pass an array of additional dependent keys as the\nsecond parameter to the macro, if your filter function relies on any external\nvalues:\n\n```javascript\nimport { filter } from '@ember/object/computed';\n\nclass Hamster {\n  constructor(chores) {\n    set(this, 'chores', chores);\n  }\n\n  doneKey = 'finished';\n\n  @filter('chores', ['doneKey'], function(chore, index, array) {\n    return !chore[this.doneKey];\n  })\n  remainingChores;\n}\n\nlet hamster = new Hamster([\n  { name: 'cook', finished: true },\n  { name: 'clean', finished: true },\n  { name: 'write more unit tests', finished: false }\n]);\n\nhamster.remainingChores; // [{name: 'write more unit tests', finished: false}]\n```",
       "itemtype": "method",
       "name": "filter",
@@ -16994,8 +17000,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.js",
-      "line": 519,
+      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.ts",
+      "line": 597,
       "description": "Filters the array by the property and value.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { filterBy } from '@ember/object/computed';\n\nclass Hamster {\n  constructor(chores) {\n    set(this, 'chores', chores);\n  }\n\n  @filterBy('chores', 'done', false) remainingChores;\n}\n\nlet hamster = new Hamster([\n  { name: 'cook', done: true },\n  { name: 'clean', done: true },\n  { name: 'write more unit tests', done: false }\n]);\n\nhamster.remainingChores; // [{ name: 'write more unit tests', done: false }]\n```",
       "itemtype": "method",
       "name": "filterBy",
@@ -17027,8 +17033,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.js",
-      "line": 575,
+      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.ts",
+      "line": 653,
       "description": "A computed property which returns a new array with all the unique elements\nfrom one or more dependent arrays.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { uniq } from '@ember/object/computed';\n\nclass Hamster {\n  constructor(fruits) {\n    set(this, 'fruits', fruits);\n  }\n\n  @uniq('fruits') uniqueFruits;\n}\n\nlet hamster = new Hamster([\n  'banana',\n  'grape',\n  'kale',\n  'banana'\n]);\n\nhamster.uniqueFruits; // ['banana', 'grape', 'kale']\n```",
       "itemtype": "method",
       "name": "uniq",
@@ -17051,8 +17057,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.js",
-      "line": 641,
+      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.ts",
+      "line": 724,
       "description": "A computed property which returns a new array with all the unique elements\nfrom an array, with uniqueness determined by specific key.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { uniqBy } from '@ember/object/computed';\n\nclass Hamster {\n  constructor(fruits) {\n    set(this, 'fruits', fruits);\n  }\n\n  @uniqBy('fruits', 'id') uniqueFruits;\n}\n\nlet hamster = new Hamster([\n  { id: 1, 'banana' },\n  { id: 2, 'grape' },\n  { id: 3, 'peach' },\n  { id: 1, 'banana' }\n]);\n\nhamster.uniqueFruits; // [ { id: 1, 'banana' }, { id: 2, 'grape' }, { id: 3, 'peach' }]\n```",
       "itemtype": "method",
       "name": "uniqBy",
@@ -17079,8 +17085,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.js",
-      "line": 695,
+      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.ts",
+      "line": 778,
       "description": "A computed property which returns a new array with all the unique elements\nfrom one or more dependent arrays.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { union } from '@ember/object/computed';\n\nclass Hamster {\n  constructor(fruits, vegetables) {\n    set(this, 'fruits', fruits);\n    set(this, 'vegetables', vegetables);\n  }\n\n  @union('fruits', 'vegetables') uniqueFruits;\n});\n\nlet hamster = new, Hamster(\n  [\n    'banana',\n    'grape',\n    'kale',\n    'banana',\n    'tomato'\n  ],\n  [\n    'tomato',\n    'carrot',\n    'lettuce'\n  ]\n);\n\nhamster.uniqueFruits; // ['banana', 'grape', 'kale', 'tomato', 'carrot', 'lettuce']\n```",
       "itemtype": "method",
       "name": "union",
@@ -17103,8 +17109,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.js",
-      "line": 742,
+      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.ts",
+      "line": 825,
       "description": "A computed property which returns a new array with all the elements\ntwo or more dependent arrays have in common.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { intersect } from '@ember/object/computed';\n\nclass FriendGroups {\n  constructor(adaFriends, charlesFriends) {\n    set(this, 'adaFriends', adaFriends);\n    set(this, 'charlesFriends', charlesFriends);\n  }\n\n  @intersect('adaFriends', 'charlesFriends') friendsInCommon;\n}\n\nlet groups = new FriendGroups(\n  ['Charles Babbage', 'John Hobhouse', 'William King', 'Mary Somerville'],\n  ['William King', 'Mary Somerville', 'Ada Lovelace', 'George Peacock']\n);\n\ngroups.friendsInCommon; // ['William King', 'Mary Somerville']\n```",
       "itemtype": "method",
       "name": "intersect",
@@ -17127,8 +17133,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.js",
-      "line": 816,
+      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.ts",
+      "line": 906,
       "description": "A computed property which returns a new array with all the properties from the\nfirst dependent array that are not in the second dependent array.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { setDiff } from '@ember/object/computed';\n\nclass Hamster {\n  constructor(likes, fruits) {\n    set(this, 'likes', likes);\n    set(this, 'fruits', fruits);\n  }\n\n  @setDiff('likes', 'fruits') wants;\n}\n\nlet hamster = new Hamster(\n  [\n    'banana',\n    'grape',\n    'kale'\n  ],\n  [\n    'grape',\n    'kale',\n  ]\n);\n\nhamster.wants; // ['banana']\n```",
       "itemtype": "method",
       "name": "setDiff",
@@ -17155,8 +17161,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.js",
-      "line": 886,
+      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.ts",
+      "line": 976,
       "description": "A computed property that returns the array of values for the provided\ndependent properties.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { collect } from '@ember/object/computed';\n\nclass Hamster {\n  @collect('hat', 'shirt') clothes;\n}\n\nlet hamster = new Hamster();\n\nhamster.clothes; // [null, null]\n\nset(hamster, 'hat', 'Camp Hat');\nset(hamster, 'shirt', 'Camp Shirt');\nhamster.clothes; // ['Camp Hat', 'Camp Shirt']\n```",
       "itemtype": "method",
       "name": "collect",
@@ -17179,8 +17185,8 @@
       "module": "@ember/object"
     },
     {
-      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.js",
-      "line": 937,
+      "file": "packages/@ember/object/lib/computed/reduce_computed_macros.ts",
+      "line": 1031,
       "description": "A computed property which returns a new array with all the properties from the\nfirst dependent array sorted based on a property or sort function. The sort\nmacro can be used in two different ways:\n\n1. By providing a sort callback function\n2. By providing an array of keys to sort the array\n\nIn the first form, the callback method you provide should have the following\nsignature:\n\n```javascript\nfunction sortCallback(itemA, itemB);\n```\n\n- `itemA` the first item to compare.\n- `itemB` the second item to compare.\n\nThis function should return negative number (e.g. `-1`) when `itemA` should\ncome before `itemB`. It should return positive number (e.g. `1`) when `itemA`\nshould come after `itemB`. If the `itemA` and `itemB` are equal this function\nshould return `0`.\n\nTherefore, if this function is comparing some numeric values, simple `itemA -\nitemB` or `itemA.get( 'foo' ) - itemB.get( 'foo' )` can be used instead of\nseries of `if`.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { sort } from '@ember/object/computed';\n\nclass ToDoList {\n  constructor(todos) {\n    set(this, 'todos', todos);\n  }\n\n  // using a custom sort function\n  @sort('todos', function(a, b){\n    if (a.priority > b.priority) {\n      return 1;\n    } else if (a.priority < b.priority) {\n      return -1;\n    }\n\n    return 0;\n  })\n  priorityTodos;\n}\n\nlet todoList = new ToDoList([\n  { name: 'Unit Test', priority: 2 },\n  { name: 'Documentation', priority: 3 },\n  { name: 'Release', priority: 1 }\n]);\n\ntodoList.priorityTodos; // [{ name:'Release', priority:1 }, { name:'Unit Test', priority:2 }, { name:'Documentation', priority:3 }]\n```\n\nYou can also optionally pass an array of additional dependent keys as the\nsecond parameter, if your sort function is dependent on additional values that\ncould changes:\n\n```js\nimport EmberObject, { set } from '@ember/object';\nimport { sort } from '@ember/object/computed';\n\nclass ToDoList {\n  sortKey = 'priority';\n\n  constructor(todos) {\n    set(this, 'todos', todos);\n  }\n\n  // using a custom sort function\n  @sort('todos', ['sortKey'], function(a, b){\n    if (a[this.sortKey] > b[this.sortKey]) {\n      return 1;\n    } else if (a[this.sortKey] < b[this.sortKey]) {\n      return -1;\n    }\n\n    return 0;\n  })\n  sortedTodos;\n});\n\nlet todoList = new ToDoList([\n  { name: 'Unit Test', priority: 2 },\n  { name: 'Documentation', priority: 3 },\n  { name: 'Release', priority: 1 }\n]);\n\ntodoList.priorityTodos; // [{ name:'Release', priority:1 }, { name:'Unit Test', priority:2 }, { name:'Documentation', priority:3 }]\n```\n\nIn the second form, you should provide the key of the array of sort values as\nthe second parameter:\n\n```javascript\nimport { set } from '@ember/object';\nimport { sort } from '@ember/object/computed';\n\nclass ToDoList {\n  constructor(todos) {\n    set(this, 'todos', todos);\n  }\n\n  // using standard ascending sort\n  todosSorting = ['name'];\n  @sort('todos', 'todosSorting') sortedTodos;\n\n  // using descending sort\n  todosSortingDesc = ['name:desc'];\n  @sort('todos', 'todosSortingDesc') sortedTodosDesc;\n}\n\nlet todoList = new ToDoList([\n  { name: 'Unit Test', priority: 2 },\n  { name: 'Documentation', priority: 3 },\n  { name: 'Release', priority: 1 }\n]);\n\ntodoList.sortedTodos; // [{ name:'Documentation', priority:3 }, { name:'Release', priority:1 }, { name:'Unit Test', priority:2 }]\ntodoList.sortedTodosDesc; // [{ name:'Unit Test', priority:2 }, { name:'Release', priority:1 }, { name:'Documentation', priority:3 }]\n```",
       "itemtype": "method",
       "name": "sort",
@@ -17335,7 +17341,7 @@
     },
     {
       "file": "packages/@ember/runloop/index.ts",
-      "line": 61,
+      "line": 62,
       "description": "Array of named queues. This array determines the order in which queues\nare flushed at the end of the RunLoop. You can define your own queues by\nsimply adding the queue name to this array. Normally you should not need\nto inspect or modify this property.",
       "itemtype": "property",
       "name": "queues",
@@ -17348,7 +17354,7 @@
     },
     {
       "file": "packages/@ember/runloop/index.ts",
-      "line": 104,
+      "line": 105,
       "description": "Runs the passed target and method inside of a RunLoop, ensuring any\ndeferred actions including bindings and views updates are flushed at the\nend.\n\nNormally you should not need to invoke this method yourself. However if\nyou are implementing raw event handlers when interfacing with other\nlibraries or plugins, you should probably wrap all of your code inside this\ncall.\n\n```javascript\nimport { run } from '@ember/runloop';\n\nrun(function() {\n  // code to be executed within a RunLoop\n});\n```",
       "itemtype": "method",
       "name": "run",
@@ -17383,7 +17389,7 @@
     },
     {
       "file": "packages/@ember/runloop/index.ts",
-      "line": 149,
+      "line": 150,
       "description": "If no run-loop is present, it creates a new one. If a run loop is\npresent it will queue itself to run on the existing run-loops action\nqueue.\n\nPlease note: This is not for normal usage, and should be used sparingly.\n\nIf invoked when not within a run loop:\n\n```javascript\nimport { join } from '@ember/runloop';\n\njoin(function() {\n  // creates a new run-loop\n});\n```\n\nAlternatively, if called within an existing run loop:\n\n```javascript\nimport { run, join } from '@ember/runloop';\n\nrun(function() {\n  // creates a new run-loop\n\n  join(function() {\n    // joins with the existing run-loop, and queues for invocation on\n    // the existing run-loops action queue.\n  });\n});\n```",
       "itemtype": "method",
       "name": "join",
@@ -17418,7 +17424,7 @@
     },
     {
       "file": "packages/@ember/runloop/index.ts",
-      "line": 208,
+      "line": 209,
       "description": "Allows you to specify which context to call the specified function in while\nadding the execution of that function to the Ember run loop. This ability\nmakes this method a great way to asynchronously integrate third-party libraries\ninto your Ember application.\n\n`bind` takes two main arguments, the desired context and the function to\ninvoke in that context. Any additional arguments will be supplied as arguments\nto the function that is passed in.\n\nLet's use the creation of a TinyMCE component as an example. Currently,\nTinyMCE provides a setup configuration option we can use to do some processing\nafter the TinyMCE instance is initialized but before it is actually rendered.\nWe can use that setup option to do some additional setup for our component.\nThe component itself could look something like the following:\n\n```app/components/rich-text-editor.js\nimport Component from '@ember/component';\nimport { on } from '@ember/object/evented';\nimport { bind } from '@ember/runloop';\n\nexport default Component.extend({\n  initializeTinyMCE: on('didInsertElement', function() {\n    tinymce.init({\n      selector: '#' + this.$().prop('id'),\n      setup: bind(this, this.setupEditor)\n    });\n  }),\n\n  didInsertElement() {\n    tinymce.init({\n      selector: '#' + this.$().prop('id'),\n      setup: bind(this, this.setupEditor)\n    });\n  }\n\n  setupEditor(editor) {\n    this.set('editor', editor);\n\n    editor.on('change', function() {\n      console.log('content changed!');\n    });\n  }\n});\n```\n\nIn this example, we use `bind` to bind the setupEditor method to the\ncontext of the RichTextEditor component and to have the invocation of that\nmethod be safely handled and executed by the Ember run loop.",
       "itemtype": "method",
       "name": "bind",
@@ -17454,7 +17460,7 @@
     },
     {
       "file": "packages/@ember/runloop/index.ts",
-      "line": 322,
+      "line": 323,
       "description": "Begins a new RunLoop. Any deferred actions invoked after the begin will\nbe buffered until you invoke a matching call to `end()`. This is\na lower-level way to use a RunLoop instead of using `run()`.\n\n```javascript\nimport { begin, end } from '@ember/runloop';\n\nbegin();\n// code to be executed within a RunLoop\nend();\n```",
       "itemtype": "method",
       "name": "begin",
@@ -17470,7 +17476,7 @@
     },
     {
       "file": "packages/@ember/runloop/index.ts",
-      "line": 345,
+      "line": 346,
       "description": "Ends a RunLoop. This must be called sometime after you call\n`begin()` to flush any deferred actions. This is a lower-level way\nto use a RunLoop instead of using `run()`.\n\n```javascript\nimport { begin, end } from '@ember/runloop';\n\nbegin();\n// code to be executed within a RunLoop\nend();\n```",
       "itemtype": "method",
       "name": "end",
@@ -17486,7 +17492,7 @@
     },
     {
       "file": "packages/@ember/runloop/index.ts",
-      "line": 368,
+      "line": 369,
       "description": "Adds the passed target/method and any optional arguments to the named\nqueue to be executed at the end of the RunLoop. If you have not already\nstarted a RunLoop when calling this method one will be started for you\nautomatically.\n\nAt the end of a RunLoop, any methods scheduled in this way will be invoked.\nMethods will be invoked in an order matching the named queues defined in\nthe `queues` property.\n\n```javascript\nimport { schedule } from '@ember/runloop';\n\nschedule('afterRender', this, function() {\n  // this will be executed in the 'afterRender' queue\n  console.log('scheduled on afterRender queue');\n});\n\nschedule('actions', this, function() {\n  // this will be executed in the 'actions' queue\n  console.log('scheduled on actions queue');\n});\n\n// Note the functions will be run in order based on the run queues order.\n// Output would be:\n//   scheduled on actions queue\n//   scheduled on afterRender queue\n```",
       "itemtype": "method",
       "name": "schedule",
@@ -17526,7 +17532,7 @@
     },
     {
       "file": "packages/@ember/runloop/index.ts",
-      "line": 441,
+      "line": 442,
       "description": "Invokes the passed target/method and optional arguments after a specified\nperiod of time. The last parameter of this method must always be a number\nof milliseconds.\n\nYou should use this method whenever you need to run some action after a\nperiod of time instead of using `setTimeout()`. This method will ensure that\nitems that expire during the same script execution cycle all execute\ntogether, which is often more efficient than using a real setTimeout.\n\n```javascript\nimport { later } from '@ember/runloop';\n\nlater(myContext, function() {\n  // code here will execute within a RunLoop in about 500ms with this == myContext\n}, 500);\n```",
       "itemtype": "method",
       "name": "later",
@@ -17566,7 +17572,7 @@
     },
     {
       "file": "packages/@ember/runloop/index.ts",
-      "line": 489,
+      "line": 490,
       "description": "Schedule a function to run one time during the current RunLoop. This is equivalent\n to calling `scheduleOnce` with the \"actions\" queue.",
       "itemtype": "method",
       "name": "once",
@@ -17601,7 +17607,7 @@
     },
     {
       "file": "packages/@ember/runloop/index.ts",
-      "line": 520,
+      "line": 521,
       "description": "Schedules a function to run one time in a given queue of the current RunLoop.\nCalling this method with the same queue/target/method combination will have\nno effect (past the initial call).\n\nNote that although you can pass optional arguments these will not be\nconsidered when looking for duplicates. New arguments will replace previous\ncalls.\n\n```javascript\nimport { run, scheduleOnce } from '@ember/runloop';\n\nfunction sayHi() {\n  console.log('hi');\n}\n\nrun(function() {\n  scheduleOnce('afterRender', myContext, sayHi);\n  scheduleOnce('afterRender', myContext, sayHi);\n  // sayHi will only be executed once, in the afterRender queue of the RunLoop\n});\n```\n\nAlso note that for `scheduleOnce` to prevent additional calls, you need to\npass the same function instance. The following case works as expected:\n\n```javascript\nfunction log() {\n  console.log('Logging only once');\n}\n\nfunction scheduleIt() {\n  scheduleOnce('actions', myContext, log);\n}\n\nscheduleIt();\nscheduleIt();\n```\n\nBut this other case will schedule the function multiple times:\n\n```javascript\nimport { scheduleOnce } from '@ember/runloop';\n\nfunction scheduleIt() {\n  scheduleOnce('actions', myContext, function() {\n    console.log('Closure');\n  });\n}\n\nscheduleIt();\nscheduleIt();\n\n// \"Closure\" will print twice, even though we're using `scheduleOnce`,\n// because the function we pass to it won't match the\n// previously scheduled operation.\n```\n\nAvailable queues, and their order, can be found at `queues`",
       "itemtype": "method",
       "name": "scheduleOnce",
@@ -17642,7 +17648,7 @@
     },
     {
       "file": "packages/@ember/runloop/index.ts",
-      "line": 614,
+      "line": 615,
       "description": "Schedules an item to run from within a separate run loop, after\ncontrol has been returned to the system. This is equivalent to calling\n`later` with a wait time of 1ms.\n\n```javascript\nimport { next } from '@ember/runloop';\n\nnext(myContext, function() {\n  // code to be executed in the next run loop,\n  // which will be scheduled after the current one\n});\n```\n\nMultiple operations scheduled with `next` will coalesce\ninto the same later run loop, along with any other operations\nscheduled by `later` that expire right around the same\ntime that `next` operations will fire.\n\nNote that there are often alternatives to using `next`.\nFor instance, if you'd like to schedule an operation to happen\nafter all DOM element operations have completed within the current\nrun loop, you can make use of the `afterRender` run loop queue (added\nby the `ember-views` package, along with the preceding `render` queue\nwhere all the DOM element operations happen).\n\nExample:\n\n```app/components/my-component.js\nimport Component from '@ember/component';\nimport { scheduleOnce } from '@ember/runloop';\n\nexport Component.extend({\n  didInsertElement() {\n    this._super(...arguments);\n    scheduleOnce('afterRender', this, 'processChildElements');\n  },\n\n  processChildElements() {\n    // ... do something with component's child component\n    // elements after they've finished rendering, which\n    // can't be done within this component's\n    // `didInsertElement` hook because that gets run\n    // before the child elements have been added to the DOM.\n  }\n});\n```\n\nOne benefit of the above approach compared to using `next` is\nthat you will be able to perform DOM/CSS operations before unprocessed\nelements are rendered to the screen, which may prevent flickering or\nother artifacts caused by delaying processing until after rendering.\n\nThe other major benefit to the above approach is that `next`\nintroduces an element of non-determinism, which can make things much\nharder to test, due to its reliance on `setTimeout`; it's much harder\nto guarantee the order of scheduled operations when they are scheduled\noutside of the current run loop, i.e. with `next`.",
       "itemtype": "method",
       "name": "next",
@@ -17677,7 +17683,7 @@
     },
     {
       "file": "packages/@ember/runloop/index.ts",
-      "line": 699,
+      "line": 700,
       "description": "Cancels a scheduled item. Must be a value returned by `later()`,\n`once()`, `scheduleOnce()`, `next()`, `debounce()`, or\n`throttle()`.\n\n```javascript\nimport {\n  next,\n  cancel,\n  later,\n  scheduleOnce,\n  once,\n  throttle,\n  debounce\n} from '@ember/runloop';\n\nlet runNext = next(myContext, function() {\n  // will not be executed\n});\n\ncancel(runNext);\n\nlet runLater = later(myContext, function() {\n  // will not be executed\n}, 500);\n\ncancel(runLater);\n\nlet runScheduleOnce = scheduleOnce('afterRender', myContext, function() {\n  // will not be executed\n});\n\ncancel(runScheduleOnce);\n\nlet runOnce = once(myContext, function() {\n  // will not be executed\n});\n\ncancel(runOnce);\n\nlet throttle = throttle(myContext, function() {\n  // will not be executed\n}, 1, false);\n\ncancel(throttle);\n\nlet debounce = debounce(myContext, function() {\n  // will not be executed\n}, 1);\n\ncancel(debounce);\n\nlet debounceImmediate = debounce(myContext, function() {\n  // will be executed since we passed in true (immediate)\n}, 100, true);\n\n// the 100ms delay until this method can be called again will be canceled\ncancel(debounceImmediate);\n```",
       "itemtype": "method",
       "name": "cancel",
@@ -17700,7 +17706,7 @@
     },
     {
       "file": "packages/@ember/runloop/index.ts",
-      "line": 770,
+      "line": 771,
       "description": "Delay calling the target method until the debounce period has elapsed\nwith no additional debounce calls. If `debounce` is called again before\nthe specified time has elapsed, the timer is reset and the entire period\nmust pass again before the target method is called.\n\nThis method should be used when an event may be called multiple times\nbut the action should only be called once when the event is done firing.\nA common example is for scroll events where you only want updates to\nhappen once scrolling has ceased.\n\n```javascript\nimport { debounce } from '@ember/runloop';\n\nfunction whoRan() {\n  console.log(this.name + ' ran.');\n}\n\nlet myContext = { name: 'debounce' };\n\ndebounce(myContext, whoRan, 150);\n\n// less than 150ms passes\ndebounce(myContext, whoRan, 150);\n\n// 150ms passes\n// whoRan is invoked with context myContext\n// console logs 'debounce ran.' one time.\n```\n\nImmediate allows you to run the function immediately, but debounce\nother calls for this function until the wait time has elapsed. If\n`debounce` is called again before the specified time has elapsed,\nthe timer is reset and the entire period must pass again before\nthe method can be called again.\n\n```javascript\nimport { debounce } from '@ember/runloop';\n\nfunction whoRan() {\n  console.log(this.name + ' ran.');\n}\n\nlet myContext = { name: 'debounce' };\n\ndebounce(myContext, whoRan, 150, true);\n\n// console logs 'debounce ran.' one time immediately.\n// 100ms passes\ndebounce(myContext, whoRan, 150, true);\n\n// 150ms passes and nothing else is logged to the console and\n// the debouncee is no longer being watched\ndebounce(myContext, whoRan, 150, true);\n\n// console logs 'debounce ran.' one time immediately.\n// 150ms passes and nothing else is logged to the console and\n// the debouncee is no longer being watched\n```",
       "itemtype": "method",
       "name": "debounce",
@@ -17745,7 +17751,7 @@
     },
     {
       "file": "packages/@ember/runloop/index.ts",
-      "line": 867,
+      "line": 868,
       "description": "Ensure that the target method is never called more frequently than\nthe specified spacing period. The target method is called immediately.\n\n```javascript\nimport { throttle } from '@ember/runloop';\n\nfunction whoRan() {\n  console.log(this.name + ' ran.');\n}\n\nlet myContext = { name: 'throttle' };\n\nthrottle(myContext, whoRan, 150);\n// whoRan is invoked with context myContext\n// console logs 'throttle ran.'\n\n// 50ms passes\nthrottle(myContext, whoRan, 150);\n\n// 50ms passes\nthrottle(myContext, whoRan, 150);\n\n// 150ms passes\nthrottle(myContext, whoRan, 150);\n// whoRan is invoked with context myContext\n// console logs 'throttle ran.'\n```",
       "itemtype": "method",
       "name": "throttle",
@@ -17790,7 +17796,7 @@
     },
     {
       "file": "packages/@ember/service/index.ts",
-      "line": 13,
+      "line": 10,
       "itemtype": "method",
       "name": "inject",
       "static": 1,
@@ -17813,7 +17819,7 @@
     },
     {
       "file": "packages/@ember/service/index.ts",
-      "line": 33,
+      "line": 30,
       "description": "Creates a property that lazily looks up a service in the container. There are\nno restrictions as to what objects a service can be injected into.\n\nExample:\n\n```app/routes/application.js\nimport Route from '@ember/routing/route';\nimport { service } from '@ember/service';\n\nexport default class ApplicationRoute extends Route {\n  @service('auth') authManager;\n\n  model() {\n    return this.authManager.findCurrentUser();\n  }\n}\n```\n\nClassic Class Example:\n\n```app/routes/application.js\nimport Route from '@ember/routing/route';\nimport { service } from '@ember/service';\n\nexport default Route.extend({\n  authManager: service('auth'),\n\n  model() {\n    return this.get('authManager').findCurrentUser();\n  }\n});\n```\n\nThis example will create an `authManager` property on the application route\nthat looks up the `auth` service in the container, making it easily accessible\nin the `model` hook.",
       "itemtype": "method",
       "name": "service",
@@ -17991,7 +17997,7 @@
     },
     {
       "file": "packages/ember-testing/lib/adapters/adapter.js",
-      "line": 19,
+      "line": 15,
       "description": "This callback will be called whenever an async operation is about to start.\n\nOverride this to call your framework's methods that handle async\noperations.",
       "access": "public",
       "tagname": "",
@@ -18002,7 +18008,7 @@
     },
     {
       "file": "packages/ember-testing/lib/adapters/adapter.js",
-      "line": 30,
+      "line": 26,
       "description": "This callback will be called whenever an async operation has completed.",
       "access": "public",
       "tagname": "",
@@ -18013,7 +18019,7 @@
     },
     {
       "file": "packages/ember-testing/lib/adapters/adapter.js",
-      "line": 38,
+      "line": 34,
       "description": "Override this method with your testing framework's false assertion.\nThis function is called whenever an exception occurs causing the testing\npromise to fail.\n\nQUnit example:\n\n```javascript\n  exception: function(error) {\n    ok(false, error);\n  };\n```",
       "access": "public",
       "tagname": "",
@@ -18486,23 +18492,23 @@
   "warnings": [
     {
       "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/-internals/container/lib/container.ts:183"
+      "line": " packages/@ember/-internals/container/lib/container.ts:185"
     },
     {
       "message": "unknown tag: internal",
-      "line": " packages/@ember/-internals/metal/lib/mixin.ts:604"
+      "line": " packages/@ember/-internals/metal/lib/mixin.ts:601"
     },
     {
       "message": "unknown tag: internal",
-      "line": " packages/@ember/-internals/metal/lib/mixin.ts:627"
+      "line": " packages/@ember/-internals/metal/lib/mixin.ts:624"
     },
     {
       "message": "unknown tag: internal",
-      "line": " packages/@ember/-internals/metal/lib/mixin.ts:648"
+      "line": " packages/@ember/-internals/metal/lib/mixin.ts:645"
     },
     {
       "message": "unknown tag: decorator",
-      "line": " packages/@ember/-internals/metal/lib/tracked.ts:17"
+      "line": " packages/@ember/-internals/metal/lib/tracked.ts:12"
     },
     {
       "message": "replacing incorrect tag: returns with return",
@@ -18514,7 +18520,7 @@
     },
     {
       "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/-internals/routing/lib/system/route.ts:2437"
+      "line": " packages/@ember/-internals/routing/lib/system/route.ts:2436"
     },
     {
       "message": "replacing incorrect tag: function with method",
@@ -18542,11 +18548,11 @@
     },
     {
       "message": "Missing item type\nThis is deprecated in favor of explicit injection of dependencies.\n\nReference: https://deprecations.emberjs.com/v3.x#toc_implicit-injections\n```\n\n@private\n@method injection\n@param {String} factoryName\n@param {String} property\n@param {String} injectionName\n@deprecated",
-      "line": " packages/@ember/-internals/container/lib/registry.ts:440"
+      "line": " packages/@ember/-internals/container/lib/registry.ts:441"
     },
     {
       "message": "Missing item type\nThe `change` and `input` actions need to be overridden in the `Input`\nsubclass. Unfortunately, some ember-source builds currently uses babel\nloose mode to transpile its classes. Having the `@action` decorator on the\nsuper class creates a getter on the prototype, and when the subclass\noverrides the method, the loose mode transpilation would emit something\nlike `Subclass.prototype['change'] = function change() { ... }`, which\nfails because `prototype['change']` is getter-only/readonly. The correct\nsolution is to use `Object.defineProperty(prototype, 'change', ...)` but\nthat requires disabling loose mode. For now, the workaround is to add the\ndecorator only on the subclass. This is more of a configuration issue on\nour own builds and doesn't really affect apps.",
-      "line": " packages/@ember/-internals/glimmer/lib/components/abstract-input.ts:125"
+      "line": " packages/@ember/-internals/glimmer/lib/components/abstract-input.ts:127"
     },
     {
       "message": "Missing item type\nThe HTML class attribute.",
@@ -18558,11 +18564,11 @@
     },
     {
       "message": "Missing item type\nThe default HTML id attribute. We don't really _need_ one, this is just\nadded for compatibility as it's hard to tell if people rely on it being\npresent, and it doens't really hurt.\n\nHowever, don't rely on this internally, like passing it to `getElementId`.\nThis can be (and often is) overriden by passing an `id` attribute on the\ninvocation, which shadows this default id via `...attributes`.",
-      "line": " packages/@ember/-internals/glimmer/lib/components/internal.ts:37"
+      "line": " packages/@ember/-internals/glimmer/lib/components/internal.ts:39"
     },
     {
       "message": "Missing item type\nThe default HTML class attribute. Similar to the above, we don't _need_\nthem, they are just added for compatibility as it's similarly hard to tell\nif people rely on it in their CSS etc, and it doens't really hurt.",
-      "line": " packages/@ember/-internals/glimmer/lib/components/internal.ts:50"
+      "line": " packages/@ember/-internals/glimmer/lib/components/internal.ts:52"
     },
     {
       "message": "Missing item type\nThis reference is used to get the `[]` tag of iterables, so we can trigger\nupdates to `{{each}}` when it changes. It is put into place by a template\ntransform at build time, similar to the (-each-in) helper",
@@ -18606,11 +18612,11 @@
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:109"
+      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:111"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:117"
+      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:119"
     },
     {
       "message": "Missing item type",
@@ -18782,11 +18788,15 @@
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/metal/lib/computed.ts:713"
+      "line": " packages/@ember/-internals/metal/lib/computed.ts:716"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/metal/lib/computed.ts:719"
+      "line": " packages/@ember/-internals/metal/lib/computed.ts:722"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/metal/lib/mixin.ts:525"
     },
     {
       "message": "Missing item type",
@@ -18806,39 +18816,35 @@
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/metal/lib/mixin.ts:540"
-    },
-    {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/metal/lib/mixin.ts:545"
+      "line": " packages/@ember/-internals/metal/lib/mixin.ts:542"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/metal/lib/mixin.ts:586"
+      "line": " packages/@ember/-internals/metal/lib/mixin.ts:583"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/metal/lib/mixin.ts:643"
+      "line": " packages/@ember/-internals/metal/lib/mixin.ts:640"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/metal/lib/mixin.ts:669"
+      "line": " packages/@ember/-internals/metal/lib/mixin.ts:666"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/metal/lib/mixin.ts:676"
+      "line": " packages/@ember/-internals/metal/lib/mixin.ts:673"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/metal/lib/mixin.ts:681"
+      "line": " packages/@ember/-internals/metal/lib/mixin.ts:678"
     },
     {
       "message": "Missing item type\nPrimarily used for cases where we are redefining a class, e.g. mixins/reopen\nbeing applied later. Revalidates all the observers, resetting their tags.",
-      "line": " packages/@ember/-internals/metal/lib/observer.ts:154"
+      "line": " packages/@ember/-internals/metal/lib/observer.ts:155"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/metal/lib/tracked.ts:17"
+      "line": " packages/@ember/-internals/metal/lib/tracked.ts:12"
     },
     {
       "message": "Missing item type",
@@ -18870,19 +18876,19 @@
     },
     {
       "message": "Missing item type\nFinds the name of the substate route if it exists for the given route. A\nsubstate route is of the form `route_state`, such as `foo_loading`.",
-      "line": " packages/@ember/-internals/routing/lib/system/router.ts:1650"
+      "line": " packages/@ember/-internals/routing/lib/system/router.ts:1646"
     },
     {
       "message": "Missing item type\nFinds the name of the state route if it exists for the given route. A state\nroute is of the form `route.state`, such as `foo.loading`. Properly Handles\n`application` named routes.",
-      "line": " packages/@ember/-internals/routing/lib/system/router.ts:1671"
+      "line": " packages/@ember/-internals/routing/lib/system/router.ts:1667"
     },
     {
       "message": "Missing item type\nDetermines whether or not a route has been defined by checking that the route\nis in the Router's map and the owner has a registration for that route.",
-      "line": " packages/@ember/-internals/routing/lib/system/router.ts:1693"
+      "line": " packages/@ember/-internals/routing/lib/system/router.ts:1689"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/mixins/container_proxy.ts:26"
+      "line": " packages/@ember/-internals/runtime/lib/mixins/container_proxy.ts:27"
     },
     {
       "message": "Missing item type\nSubscribes to a named event with given function.",
@@ -18958,47 +18964,47 @@
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/system/array_proxy.ts:134"
+      "line": " packages/@ember/-internals/runtime/lib/system/array_proxy.ts:128"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/system/array_proxy.ts:136"
+      "line": " packages/@ember/-internals/runtime/lib/system/array_proxy.ts:130"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/system/array_proxy.ts:139"
+      "line": " packages/@ember/-internals/runtime/lib/system/array_proxy.ts:133"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/system/array_proxy.ts:141"
+      "line": " packages/@ember/-internals/runtime/lib/system/array_proxy.ts:135"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/system/array_proxy.ts:144"
+      "line": " packages/@ember/-internals/runtime/lib/system/array_proxy.ts:138"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/system/array_proxy.ts:146"
+      "line": " packages/@ember/-internals/runtime/lib/system/array_proxy.ts:140"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/system/array_proxy.ts:148"
+      "line": " packages/@ember/-internals/runtime/lib/system/array_proxy.ts:142"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/system/array_proxy.ts:150"
+      "line": " packages/@ember/-internals/runtime/lib/system/array_proxy.ts:144"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/system/array_proxy.ts:152"
+      "line": " packages/@ember/-internals/runtime/lib/system/array_proxy.ts:146"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/system/array_proxy.ts:154"
+      "line": " packages/@ember/-internals/runtime/lib/system/array_proxy.ts:148"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/system/core_object.ts:236"
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.ts:235"
     },
     {
       "message": "Missing item type",
@@ -19018,43 +19024,43 @@
     },
     {
       "message": "Missing item type\nUnfortunately, a lot of existing code assumes the booting process is\n\"synchronous\". Specifically, a lot of tests assumes the last call to\n`app.advanceReadiness()` or `app.reset()` will result in the app being\nfully-booted when the current runloop completes.\n\nWe would like new code (like the `visit` API) to stop making this assumption,\nso we created the asynchronous version above that returns a promise. But until\nwe have migrated all the code, we would have to expose this method for use\n*internally* in places where we need to boot an app \"synchronously\".",
-      "line": " packages/@ember/application/lib/application.ts:735"
+      "line": " packages/@ember/application/lib/application.ts:737"
     },
     {
       "message": "Missing item type\nOverrides the base `EngineInstance._bootSync` method with concerns relevant\nto booting application (instead of engine) instances.\n\nThis method should only contain synchronous boot concerns. Asynchronous\nboot concerns should eventually be moved to the `boot` method, which\nreturns a promise.\n\nUntil all boot code has been made asynchronous, we need to continue to\nexpose this method for use *internally* in places where we need to boot an\ninstance synchronously.",
-      "line": " packages/@ember/application/instance.ts:88"
+      "line": " packages/@ember/application/instance.ts:89"
     },
     {
       "message": "Missing item type\nThis hook is called by the root-most Route (a.k.a. the ApplicationRoute)\nwhen it has finished creating the root View. By default, we simply take the\nview and append it to the `rootElement` specified on the Application.\n\nIn cases like FastBoot and testing, we can override this hook and implement\ncustom behavior, such as serializing to a string and sending over an HTTP\nsocket rather than appending to DOM.",
-      "line": " packages/@ember/application/instance.ts:148"
+      "line": " packages/@ember/application/instance.ts:149"
     },
     {
       "message": "Missing item type\nTells the router to start routing. The router will ask the location for the\ncurrent URL of the page to determine the initial URL to start routing to.\nTo start the app at a specific URL, call `handleURL` instead.",
-      "line": " packages/@ember/application/instance.ts:165"
+      "line": " packages/@ember/application/instance.ts:166"
     },
     {
       "message": "Missing item type\nSets up the router, initializing the child router and configuring the\nlocation before routing begins.\n\nBecause setup should only occur once, multiple calls to `setupRouter`\nbeyond the first call have no effect.\n\nThis is commonly used in order to confirm things that rely on the router\nare functioning properly from tests that are primarily rendering related.\n\nFor example, from within [ember-qunit](https://github.com/emberjs/ember-qunit)'s\n`setupRenderingTest` calling `this.owner.setupRouter()` would allow that\nrendering test to confirm that any `<LinkTo></LinkTo>`'s that are rendered\nhave the correct URL.",
-      "line": " packages/@ember/application/instance.ts:176"
+      "line": " packages/@ember/application/instance.ts:177"
     },
     {
       "message": "Missing item type\nDirects the router to route to a particular URL. This is useful in tests,\nfor example, to tell the app to start at a particular URL.",
-      "line": " packages/@ember/application/instance.ts:197"
+      "line": " packages/@ember/application/instance.ts:198"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/application/instance.ts:209"
+      "line": " packages/@ember/application/instance.ts:210"
     },
     {
       "message": "Missing item type\nReturns the current URL of the app instance. This is useful when your\napp does not update the browsers URL bar (i.e. it uses the `'none'`\nlocation adapter).",
-      "line": " packages/@ember/application/instance.ts:231"
+      "line": " packages/@ember/application/instance.ts:232"
     },
     {
       "message": "Missing item type\nNavigate the instance to a particular URL. This is useful in tests, for\nexample, or to tell the app to start at a particular URL. This method\nreturns a promise that resolves with the app instance when the transition\nis complete, or rejects if the transion was aborted due to an error.",
-      "line": " packages/@ember/application/instance.ts:246"
+      "line": " packages/@ember/application/instance.ts:247"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/controller/lib/controller_mixin.d.ts:11"
+      "line": " packages/@ember/controller/lib/controller_mixin.ts:24"
     },
     {
       "message": "Missing item type\nUnfortunately, a lot of existing code assumes booting an instance is\nsynchronous – specifically, a lot of tests assume the last call to\n`app.advanceReadiness()` or `app.reset()` will result in a new instance\nbeing fully-booted when the current runloop completes.\n\nWe would like new code (like the `visit` API) to stop making this\nassumption, so we created the asynchronous version above that returns a\npromise. But until we have migrated all the code, we would have to expose\nthis method for use *internally* in places where we need to boot an instance\nsynchronously.",