ember-source 5.6.0-alpha.2 → 5.6.0-alpha.3

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": "5.6.0-alpha.2"
+    "version": "5.6.0-alpha.3"
   },
   "files": {
     "node_modules/rsvp/lib/rsvp/promise/all.js": {
@@ -2260,7 +2260,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/object/core.ts",
-      "line": 175
+      "line": 174
     },
     "@ember/object/evented": {
       "name": "@ember/object/evented",
@@ -2289,7 +2289,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/object/mixin.ts",
-      "line": 455
+      "line": 454
     },
     "@ember/object/observable": {
       "name": "@ember/object/observable",
@@ -2429,7 +2429,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/routing/route.ts",
-      "line": 79
+      "line": 80
     },
     "@ember/routing/router-service": {
       "name": "@ember/routing/router-service",
@@ -2455,7 +2455,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/routing/router.ts",
-      "line": 145
+      "line": 126
     },
     "@ember/routing/transition": {
       "name": "@ember/routing/transition",
@@ -2868,7 +2868,7 @@
       "module": "@ember/object",
       "namespace": "",
       "file": "packages/@ember/-internals/metal/lib/decorator.ts",
-      "line": 50,
+      "line": 49,
       "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": ""
@@ -3832,7 +3832,7 @@
       "module": "@ember/object/core",
       "namespace": "",
       "file": "packages/@ember/object/core.ts",
-      "line": 175,
+      "line": 174,
       "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": ""
@@ -3888,7 +3888,7 @@
       "module": "@ember/object/mixin",
       "namespace": "",
       "file": "packages/@ember/object/mixin.ts",
-      "line": 455,
+      "line": 454,
       "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": ""
@@ -4129,7 +4129,7 @@
       "module": "@ember/routing/route",
       "namespace": "",
       "file": "packages/@ember/routing/route.ts",
-      "line": 79,
+      "line": 80,
       "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": [
@@ -4168,7 +4168,7 @@
       "module": "@ember/routing/router",
       "namespace": "",
       "file": "packages/@ember/routing/router.ts",
-      "line": 145,
+      "line": 126,
       "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": [
@@ -5598,7 +5598,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/components/link-to.ts",
-      "line": 43,
+      "line": 44,
       "description": "The `LinkTo` component renders a link to the supplied `routeName` passing an optionally\nsupplied model to the route as its `model` context of the route. The block for `LinkTo`\nbecomes the contents of the rendered element:\n\n```handlebars\n<LinkTo @route='photoGallery'>\n  Great Hamster Photos\n</LinkTo>\n```\n\nThis will result in:\n\n```html\n<a href=\"/hamster-photos\">\n  Great Hamster Photos\n</a>\n```\n\n### Disabling the `LinkTo` component\n\nThe `LinkTo` component can be disabled by using the `disabled` argument. A disabled link\ndoesn't result in a transition when activated, and adds the `disabled` class to the `<a>`\nelement.\n\n(The class name to apply to the element can be overridden by using the `disabledClass`\nargument)\n\n```handlebars\n<LinkTo @route='photoGallery' @disabled={{true}}>\n  Great Hamster Photos\n</LinkTo>\n```\n\n### Handling `href`\n\n`<LinkTo>` will use your application's Router to fill the element's `href` property with a URL\nthat matches the path to the supplied `routeName`.\n\n### Handling current route\n\nThe `LinkTo` component will apply a CSS class name of 'active' when the application's current\nroute matches the supplied routeName. For example, if the application's current route is\n'photoGallery.recent', then the following invocation of `LinkTo`:\n\n```handlebars\n<LinkTo @route='photoGallery.recent'>\n  Great Hamster Photos\n</LinkTo>\n```\n\nwill result in\n\n```html\n<a href=\"/hamster-photos/this-week\" class=\"active\">\n  Great Hamster Photos\n</a>\n```\n\nThe CSS class used for active classes can be customized by passing an `activeClass` argument:\n\n```handlebars\n<LinkTo @route='photoGallery.recent' @activeClass=\"current-url\">\n  Great Hamster Photos\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/this-week\" class=\"current-url\">\n  Great Hamster Photos\n</a>\n```\n\n### Keeping a link active for other routes\n\nIf you need a link to be 'active' even when it doesn't match the current route, you can use the\n`current-when` argument.\n\n```handlebars\n<LinkTo @route='photoGallery' @current-when='photos'>\n  Photo Gallery\n</LinkTo>\n```\n\nThis may be helpful for keeping links active for:\n\n* non-nested routes that are logically related\n* some secondary menu approaches\n* 'top navigation' with 'sub navigation' scenarios\n\nA link will be active if `current-when` is `true` or the current\nroute is the route this link would transition to.\n\nTo match multiple routes 'space-separate' the routes:\n\n```handlebars\n<LinkTo @route='gallery' @current-when='photos drawings paintings'>\n  Art Gallery\n</LinkTo>\n```\n\n### Supplying a model\n\nAn optional `model` argument can be used for routes whose\npaths contain dynamic segments. This argument will become\nthe model context of the linked route:\n\n```javascript\nRouter.map(function() {\n  this.route(\"photoGallery\", {path: \"hamster-photos/:photo_id\"});\n});\n```\n\n```handlebars\n<LinkTo @route='photoGallery' @model={{this.aPhoto}}>\n  {{aPhoto.title}}\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/42\">\n  Tomster\n</a>\n```\n\n### Supplying multiple models\n\nFor deep-linking to route paths that contain multiple\ndynamic segments, the `models` argument can be used.\n\nAs the router transitions through the route path, each\nsupplied model argument will become the context for the\nroute with the dynamic segments:\n\n```javascript\nRouter.map(function() {\n  this.route(\"photoGallery\", { path: \"hamster-photos/:photo_id\" }, function() {\n    this.route(\"comment\", {path: \"comments/:comment_id\"});\n  });\n});\n```\n\nThis argument will become the model context of the linked route:\n\n```handlebars\n<LinkTo @route='photoGallery.comment' @models={{array this.aPhoto this.comment}}>\n  {{comment.body}}\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/42/comments/718\">\n  A+++ would snuggle again.\n</a>\n```\n\n### Supplying an explicit dynamic segment value\n\nIf you don't have a model object available to pass to `LinkTo`,\nan optional string or integer argument can be passed for routes whose\npaths contain dynamic segments. This argument will become the value\nof the dynamic segment:\n\n```javascript\nRouter.map(function() {\n  this.route(\"photoGallery\", { path: \"hamster-photos/:photo_id\" });\n});\n```\n\n```handlebars\n<LinkTo @route='photoGallery' @model={{aPhotoId}}>\n  {{this.aPhoto.title}}\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/42\">\n  Tomster\n</a>\n```\n\nWhen transitioning into the linked route, the `model` hook will\nbe triggered with parameters including this passed identifier.\n\n### Supplying query parameters\n\nIf you need to add optional key-value pairs that appear to the right of the ? in a URL,\nyou can use the `query` argument.\n\n```handlebars\n<LinkTo @route='photoGallery' @query={{hash page=1 per_page=20}}>\n  Great Hamster Photos\n</LinkTo>\n```\n\nThis will result in:\n\n```html\n<a href=\"/hamster-photos?page=1&per_page=20\">\n  Great Hamster Photos\n</a>\n```",
       "itemtype": "method",
       "name": "LinkTo",
@@ -5609,7 +5609,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/components/link-to.ts",
-      "line": 255,
+      "line": 256,
       "description": "See [Ember.Templates.components.LinkTo](/ember/release/classes/Ember.Templates.components/methods/input?anchor=LinkTo).",
       "itemtype": "method",
       "name": "link-to",
@@ -5623,7 +5623,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/components/link-to.ts",
-      "line": 264,
+      "line": 265,
       "description": "An opaque interface which can be imported and used in strict-mode\ntemplates to call <LinkTo>.\n\nSee [Ember.Templates.components.LinkTo](/ember/release/classes/Ember.Templates.components/methods/input?anchor=LinkTo).",
       "itemtype": "method",
       "name": "LinkTo",
@@ -5683,7 +5683,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/helpers/action.ts",
-      "line": 18,
+      "line": 17,
       "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",
@@ -5988,7 +5988,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/syntax/mount.ts",
-      "line": 16,
+      "line": 17,
       "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",
@@ -6012,7 +6012,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/syntax/outlet.ts",
-      "line": 22,
+      "line": 21,
       "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",
@@ -6050,64 +6050,74 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/utils/outlet.ts",
-      "line": 5,
-      "description": "Not sure why this is here, we use the owner of the template for lookups.\n\nMaybe this is for the render helper?",
+      "line": 21,
+      "description": "This is usually inherited from the parent (all the way up to the app\ninstance). However, engines uses this to swap out the owner when crossing\na mount point.",
       "class": "@ember/template",
       "module": "ember"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/utils/outlet.ts",
-      "line": 12,
-      "description": "The name of the parent outlet state.",
+      "line": 28,
+      "deprecated": true,
+      "deprecationMessage": "This used to specify \"which parent route to render into\",\nwhich is not a thing anymore.",
       "class": "@ember/template",
       "module": "ember"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/utils/outlet.ts",
-      "line": 22,
+      "line": 34,
+      "deprecated": true,
+      "deprecationMessage": "This used to specify \"which named outlet in the parent\ntemplate to render into\", which is not a thing anymore.",
+      "class": "@ember/template",
+      "module": "ember"
+    },
+    {
+      "file": "packages/@ember/-internals/glimmer/lib/utils/outlet.ts",
+      "line": 40,
       "description": "The name of the route/template",
       "class": "@ember/template",
       "module": "ember"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/utils/outlet.ts",
-      "line": 27,
+      "line": 45,
       "description": "The controller (the self of the outlet component)",
       "class": "@ember/template",
       "module": "ember"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/utils/outlet.ts",
-      "line": 32,
+      "line": 50,
       "description": "The model (the resolved value of the model hook)",
       "class": "@ember/template",
       "module": "ember"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/utils/outlet.ts",
-      "line": 37,
+      "line": 55,
       "description": "template (the layout of the outlet component)",
       "class": "@ember/template",
       "module": "ember"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/utils/outlet.ts",
-      "line": 48,
-      "description": "Nested outlet connections.",
+      "line": 62,
+      "description": "Represents what was rendered into this outlet.",
       "class": "@ember/template",
       "module": "ember"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/utils/outlet.ts",
-      "line": 53,
-      "description": "Represents what was rendered into this outlet.",
+      "line": 67,
+      "description": "Represents what, if any, should be rendered into the next {{outlet}} found\nat this level.\n\nThis used to be a dictionary of children outlets, including the {{outlet}}\n\"main\" outlet any {{outlet \"named\"}} named outlets. Since named outlets\nare not a thing anymore, this can now just be a single`child`.",
       "class": "@ember/template",
       "module": "ember"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/utils/outlet.ts",
-      "line": 58,
-      "description": "Has to do with render helper and orphan outlets.\nWhether outlet state was rendered.",
+      "line": 79,
+      "deprecated": true,
+      "deprecationMessage": "This tracks whether this outlet state actually made it onto the page\nsomewhere. This was more of a problem when you can declare named outlets\nleft and right, and anything can render into anywhere else. We want to\nwarn users when you tried to render into somewhere that does not exist,\nbut we don't know what named outlets exists until after we have rendered\neverything, so this was used to track these orphan renders.\n\nThis can still happen, if, according to the router, a route is active and\nso its template should be rendered, but the parent template is missing the\n`{{outlet}}` keyword, or that it was hidden by an `{{#if}}` or something.\nI guess that is considered valid, because nothing checks for this anymore.\nseems valid for the parent to decide not to render a child template?",
       "class": "@ember/template",
       "module": "ember"
     },
@@ -6182,13 +6192,13 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/views/outlet.ts",
-      "line": 118,
+      "line": 116,
       "class": "Component",
       "module": "@ember/template"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/views/outlet.ts",
-      "line": 126,
+      "line": 124,
       "class": "Component",
       "module": "@ember/template"
     },
@@ -6516,7 +6526,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/renderer.ts",
-      "line": 298,
+      "line": 299,
       "class": "Ember.Templates.helpers",
       "module": "@ember/component"
     },
@@ -7012,7 +7022,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/decorator.ts",
-      "line": 157,
+      "line": 156,
       "description": "Returns the CP descriptor associated with `obj` and `keyName`, if any.",
       "itemtype": "method",
       "name": "descriptorForProperty",
@@ -7039,7 +7049,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/decorator.ts",
-      "line": 185,
+      "line": 184,
       "description": "Check whether a value is a decorator",
       "itemtype": "method",
       "name": "isClassicDecorator",
@@ -7061,7 +7071,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/decorator.ts",
-      "line": 197,
+      "line": 196,
       "description": "Set a value as a decorator",
       "itemtype": "method",
       "name": "setClassicDecorator",
@@ -8572,7 +8582,7 @@
     },
     {
       "file": "packages/@ember/-internals/utils/lib/super.ts",
-      "line": 73,
+      "line": 71,
       "description": "Wraps the passed function so that `this._super` will point to the superFunc\nwhen the function is invoked. This is the primitive we use to implement\ncalls to super.",
       "access": "private",
       "tagname": "",
@@ -9042,7 +9052,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 35,
+      "line": 37,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -9059,7 +9069,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 57,
+      "line": 59,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -9076,7 +9086,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 77,
+      "line": 79,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -9093,7 +9103,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 109,
+      "line": 111,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -9110,7 +9120,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 152,
+      "line": 154,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -9127,7 +9137,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 161,
+      "line": 163,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -9144,7 +9154,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 176,
+      "line": 178,
       "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": "",
@@ -9162,7 +9172,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 192,
+      "line": 194,
       "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": "",
@@ -9180,7 +9190,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 208,
+      "line": 210,
       "description": "Determines if the element matches the specified selector.",
       "access": "private",
       "tagname": "",
@@ -11648,7 +11658,7 @@
     },
     {
       "file": "packages/@ember/debug/lib/inspect.ts",
-      "line": 15,
+      "line": 14,
       "description": "Convenience method to inspect an object. This method will attempt to\nconvert the object into a useful string description.\n\nIt is a pretty simple implementation. If you want something more robust,\nuse something like JSDump: https://github.com/NV/jsDump",
       "itemtype": "method",
       "name": "inspect",
@@ -13926,19 +13936,19 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 237,
+      "line": 236,
       "class": "CoreObject",
       "module": "@ember/object/core"
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 241,
+      "line": 240,
       "class": "CoreObject",
       "module": "@ember/object/core"
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 322,
+      "line": 321,
       "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",
@@ -13949,7 +13959,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 356,
+      "line": 355,
       "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",
@@ -13962,7 +13972,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 430,
+      "line": 429,
       "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",
@@ -13975,7 +13985,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 505,
+      "line": 504,
       "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",
@@ -13987,7 +13997,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 523,
+      "line": 522,
       "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",
@@ -13999,7 +14009,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 541,
+      "line": 540,
       "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",
@@ -14014,7 +14024,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 568,
+      "line": 567,
       "description": "Override to implement teardown.",
       "itemtype": "method",
       "name": "willDestroy",
@@ -14025,7 +14035,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 576,
+      "line": 575,
       "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",
@@ -14040,7 +14050,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 621,
+      "line": 620,
       "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",
@@ -14068,7 +14078,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 725,
+      "line": 724,
       "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",
@@ -14088,7 +14098,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 810,
+      "line": 809,
       "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",
@@ -14100,7 +14110,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 864,
+      "line": 863,
       "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",
@@ -14112,7 +14122,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 950,
+      "line": 949,
       "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",
@@ -14131,7 +14141,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 993,
+      "line": 992,
       "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",
@@ -14155,7 +14165,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 1085,
+      "line": 1084,
       "description": "Provides lookup-time type validation for injected properties.",
       "access": "private",
       "tagname": "",
@@ -14166,7 +14176,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 1106,
+      "line": 1105,
       "description": "Returns a hash of property names and container names that injected\nproperties will lookup on the container lazily.",
       "itemtype": "method",
       "name": "_lazyInjections",
@@ -14372,7 +14382,7 @@
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 441,
+      "line": 440,
       "itemtype": "method",
       "name": "mixin",
       "params": [
@@ -14396,43 +14406,43 @@
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 538,
+      "line": 537,
       "class": "Mixin",
       "module": "@ember/object/mixin"
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 541,
+      "line": 540,
       "class": "Mixin",
       "module": "@ember/object/mixin"
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 544,
+      "line": 543,
       "class": "Mixin",
       "module": "@ember/object/mixin"
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 547,
+      "line": 546,
       "class": "Mixin",
       "module": "@ember/object/mixin"
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 550,
+      "line": 549,
       "class": "Mixin",
       "module": "@ember/object/mixin"
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 555,
+      "line": 554,
       "class": "Mixin",
       "module": "@ember/object/mixin"
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 581,
+      "line": 580,
       "itemtype": "method",
       "name": "create",
       "static": 1,
@@ -14450,13 +14460,13 @@
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 596,
+      "line": 595,
       "class": "@ember/object/mixin",
       "module": "@ember/object/mixin"
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 614,
+      "line": 613,
       "itemtype": "method",
       "name": "reopen",
       "params": [
@@ -14474,7 +14484,7 @@
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 637,
+      "line": 636,
       "itemtype": "method",
       "name": "apply",
       "params": [
@@ -14494,13 +14504,13 @@
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 653,
+      "line": 652,
       "class": "@ember/object/mixin",
       "module": "@ember/object/mixin"
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 658,
+      "line": 657,
       "itemtype": "method",
       "name": "detect",
       "params": [
@@ -14521,19 +14531,19 @@
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 679,
+      "line": 678,
       "class": "@ember/object/mixin",
       "module": "@ember/object/mixin"
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 686,
+      "line": 685,
       "class": "@ember/object/mixin",
       "module": "@ember/object/mixin"
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 693,
+      "line": 692,
       "class": "@ember/object/mixin",
       "module": "@ember/object/mixin"
     },
@@ -15732,7 +15742,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 91,
+      "line": 92,
       "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.router.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",
@@ -15751,7 +15761,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 136,
+      "line": 137,
       "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    // your code there\n    return true; // Bubble the didTransition event\n  }\n}\n```",
       "itemtype": "event",
       "name": "didTransition",
@@ -15763,7 +15773,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 163,
+      "line": 164,
       "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",
@@ -15787,7 +15797,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 198,
+      "line": 199,
       "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';\nimport { service } from '@ember/service';\n\nexport default class AdminRoute extends Route {\n  @service router;\n\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.router.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",
@@ -15811,31 +15821,31 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 271,
+      "line": 272,
       "class": "Route",
       "module": "@ember/routing/route"
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 273,
+      "line": 274,
       "class": "Route",
       "module": "@ember/routing/route"
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 276,
+      "line": 277,
       "class": "Route",
       "module": "@ember/routing/route"
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 278,
+      "line": 279,
       "class": "Route",
       "module": "@ember/routing/route"
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 306,
+      "line": 307,
       "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",
@@ -15863,7 +15873,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 374,
+      "line": 375,
       "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",
@@ -15876,7 +15886,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 427,
+      "line": 428,
       "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",
@@ -15890,7 +15900,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 460,
+      "line": 461,
       "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",
@@ -15904,7 +15914,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 483,
+      "line": 484,
       "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",
@@ -15917,7 +15927,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 514,
+      "line": 515,
       "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",
@@ -15930,7 +15940,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 528,
+      "line": 529,
       "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",
@@ -15943,7 +15953,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 543,
+      "line": 544,
       "description": "Sets the name for this route, including a fully resolved name for routes\ninside engines.",
       "access": "private",
       "tagname": "",
@@ -15961,7 +15971,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 558,
+      "line": 559,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -15971,7 +15981,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 592,
+      "line": 593,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -15981,7 +15991,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 601,
+      "line": 602,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -15991,7 +16001,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 609,
+      "line": 610,
       "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",
@@ -16014,7 +16024,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 690,
+      "line": 691,
       "description": "Serializes the query parameter key",
       "itemtype": "method",
       "name": "serializeQueryParamKey",
@@ -16032,7 +16042,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 701,
+      "line": 702,
       "description": "Serializes value of the query parameter based on defaultValueType",
       "itemtype": "method",
       "name": "serializeQueryParam",
@@ -16060,7 +16070,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 717,
+      "line": 718,
       "description": "Deserializes value of the query parameter based on defaultValueType",
       "itemtype": "method",
       "name": "deserializeQueryParam",
@@ -16088,7 +16098,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 733,
+      "line": 734,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -16098,7 +16108,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 749,
+      "line": 750,
       "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",
@@ -16127,7 +16137,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 779,
+      "line": 780,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -16137,7 +16147,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 790,
+      "line": 791,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -16148,7 +16158,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 804,
+      "line": 805,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -16158,7 +16168,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 815,
+      "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",
@@ -16170,7 +16180,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 835,
+      "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",
@@ -16182,7 +16192,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 855,
+      "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",
@@ -16201,7 +16211,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 866,
+      "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",
@@ -16220,7 +16230,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 877,
+      "line": 878,
       "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",
@@ -16244,7 +16254,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 899,
+      "line": 900,
       "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",
@@ -16260,7 +16270,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 925,
+      "line": 926,
       "description": "This hook is the entry point for router.js",
       "access": "private",
       "tagname": "",
@@ -16271,7 +16281,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1000,
+      "line": 1001,
       "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`router.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",
@@ -16294,7 +16304,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1035,
+      "line": 1036,
       "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';\nimport { service } from '@ember/service';\n\nexport default class PostsRoute extends Route {\n  @service router;\n\n  afterModel(posts, transition) {\n    if (posts.get('length') === 1) {\n      this.router.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",
@@ -16322,7 +16332,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1079,
+      "line": 1080,
       "description": "A hook you can implement to optionally redirect to another route.\n\nCalling `this.router.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.router.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",
@@ -16346,7 +16356,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1104,
+      "line": 1105,
       "description": "Called when the context is changed by router.js.",
       "access": "private",
       "tagname": "",
@@ -16357,7 +16367,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1114,
+      "line": 1115,
       "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\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.router.transitionTo('posts');\n\n// model passed in, so model hook not called\nthePost = store.findRecord('post', 1);\nthis.router.transitionTo('post', thePost);\n\n// integer passed in, model hook is called\nthis.router.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.router.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\nNote that the legacy behavior of automatically defining a model\nhook when a dynamic segment ending in `_id` is present is\n[deprecated](https://deprecations.emberjs.com/v5.x#toc_deprecate-implicit-route-model).\nYou should explicitly define a model hook whenever any segments are\npresent.\n\nExample\n\n```app/routes/post.js\nimport Route from '@ember/routing/route';\nimport { service } from '@ember/service';\n\nexport default class PostRoute extends Route {\n  @service store;\n\n  model(params) {\n    return this.store.findRecord('post', params.post_id);\n  }\n}\n```",
       "itemtype": "method",
       "name": "model",
@@ -16385,7 +16395,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1232,
+      "line": 1233,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -16411,7 +16421,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1245,
+      "line": 1246,
       "itemtype": "method",
       "name": "findModel",
       "params": [
@@ -16433,7 +16443,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1273,
+      "line": 1274,
       "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';\nimport { service } from '@ember/service';\n\nexport default class PhotosRoute extends Route {\n  @service store;\n\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```"
@@ -16466,7 +16476,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1352,
+      "line": 1353,
       "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",
@@ -16489,7 +16499,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1406,
+      "line": 1407,
       "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",
@@ -16507,7 +16517,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1434,
+      "line": 1435,
       "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",
@@ -16530,49 +16540,10 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1506,
-      "description": "`this[RENDER]` is used to render a template into a region of another template\n(indicated by an `{{outlet}}`).",
+      "line": 1509,
+      "description": "`this[RENDER]` is used to set up the rendering option for the outlet state.",
       "itemtype": "method",
       "name": "this[RENDER]",
-      "params": [
-        {
-          "name": "name",
-          "description": "the name of the template to render",
-          "type": "String"
-        },
-        {
-          "name": "options",
-          "description": "the options",
-          "type": "Object",
-          "optional": true,
-          "props": [
-            {
-              "name": "into",
-              "description": "the template to render into,\n                referenced by name. Defaults to the parent template",
-              "type": "String",
-              "optional": true
-            },
-            {
-              "name": "outlet",
-              "description": "the outlet inside `options.into` to render into.\n                Defaults to 'main'",
-              "type": "String",
-              "optional": true
-            },
-            {
-              "name": "controller",
-              "description": "the controller to use for this template,\n                referenced by name or as a controller instance. Defaults to the Route's paired controller",
-              "type": "String|Object",
-              "optional": true
-            },
-            {
-              "name": "model",
-              "description": "the model object to set on `options.controller`.\n                Defaults to the return value of the Route's model hook",
-              "type": "Object",
-              "optional": true
-            }
-          ]
-        }
-      ],
       "access": "private",
       "tagname": "",
       "class": "Route",
@@ -16580,7 +16551,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1533,
+      "line": 1523,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -16590,7 +16561,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1546,
+      "line": 1535,
       "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",
@@ -16605,13 +16576,13 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1597,
+      "line": 1586,
       "class": "Route",
       "module": "@ember/routing/route"
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1646,
+      "line": 1635,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -16621,7 +16592,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1785,
+      "line": 1774,
       "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",
@@ -16645,7 +16616,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 2168,
+      "line": 2054,
       "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",
@@ -16658,7 +16629,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 2199,
+      "line": 2085,
       "description": "This action is called when one or more query params have changed. Bubbles.",
       "itemtype": "method",
       "name": "queryParamsDidChange",
@@ -17035,7 +17006,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 155,
+      "line": 136,
       "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",
@@ -17047,7 +17018,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 166,
+      "line": 147,
       "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 `history` by the `locationType` setting of `/config/environment.js`",
       "itemtype": "property",
       "name": "location",
@@ -17062,7 +17033,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 224,
+      "line": 205,
       "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",
@@ -17079,7 +17050,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 559,
+      "line": 540,
       "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",
@@ -17090,7 +17061,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 705,
+      "line": 696,
       "description": "Transition the application into another route. The route may\nbe either a single route or route path:",
       "itemtype": "method",
       "name": "transitionTo",
@@ -17124,7 +17095,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 750,
+      "line": 741,
       "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",
@@ -17158,7 +17129,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 777,
+      "line": 768,
       "description": "Determines if the supplied route is currently active.",
       "itemtype": "method",
       "name": "isActive",
@@ -17179,7 +17150,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 789,
+      "line": 780,
       "description": "An alternative form of `isActive` that doesn't require\nmanual concatenation of the arguments into a single\narray.",
       "itemtype": "method",
       "name": "isActiveIntent",
@@ -17209,7 +17180,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 815,
+      "line": 806,
       "description": "Does this router instance have the given route.",
       "itemtype": "method",
       "name": "hasRoute",
@@ -17224,7 +17195,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 826,
+      "line": 817,
       "description": "Resets the state of the router by clearing the current route\nhandlers and deactivating them.",
       "access": "private",
       "tagname": "",
@@ -17235,7 +17206,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 925,
+      "line": 916,
       "description": "Serializes the given query params according to their QP meta information.",
       "access": "private",
       "tagname": "",
@@ -17262,7 +17233,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 955,
+      "line": 946,
       "description": "Serializes the value of a query parameter based on a type",
       "access": "private",
       "tagname": "",
@@ -17285,7 +17256,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 973,
+      "line": 964,
       "description": "Deserializes the given query params according to their QP meta information.",
       "access": "private",
       "tagname": "",
@@ -17312,7 +17283,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1001,
+      "line": 992,
       "description": "Deserializes the value of a query parameter based on a default type",
       "access": "private",
       "tagname": "",
@@ -17335,7 +17306,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1022,
+      "line": 1013,
       "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": "",
@@ -17362,7 +17333,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1103,
+      "line": 1094,
       "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": "",
@@ -17399,7 +17370,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1130,
+      "line": 1121,
       "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": "",
@@ -17421,7 +17392,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1144,
+      "line": 1135,
       "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": "",
@@ -17443,7 +17414,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1206,
+      "line": 1197,
       "description": "Maps all query param keys to their fully scoped property name of the form\n`controllerName:propName`.",
       "access": "private",
       "tagname": "",
@@ -17475,7 +17446,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1248,
+      "line": 1239,
       "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": "",
@@ -17502,7 +17473,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1419,
+      "line": 1410,
       "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",
@@ -17514,7 +17485,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1456,
+      "line": 1447,
       "description": "Handles notifying any listeners of an impending URL\nchange.\n\nTriggers the router level `willTransition` hook.",
       "itemtype": "method",
       "name": "willTransition",
@@ -17526,7 +17497,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1469,
+      "line": 1460,
       "description": "Represents the current URL.",
       "itemtype": "property",
       "name": "url",
@@ -17538,7 +17509,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1632,
+      "line": 1623,
       "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": "",
@@ -17563,7 +17534,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1653,
+      "line": 1644,
       "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": "",
@@ -17588,7 +17559,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1675,
+      "line": 1666,
       "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": "",
@@ -19117,15 +19088,15 @@
     },
     {
       "message": "unknown tag: internal",
-      "line": " packages/@ember/object/mixin.ts:614"
+      "line": " packages/@ember/object/mixin.ts:613"
     },
     {
       "message": "unknown tag: internal",
-      "line": " packages/@ember/object/mixin.ts:637"
+      "line": " packages/@ember/object/mixin.ts:636"
     },
     {
       "message": "unknown tag: internal",
-      "line": " packages/@ember/object/mixin.ts:658"
+      "line": " packages/@ember/object/mixin.ts:657"
     },
     {
       "message": "replacing incorrect tag: returns with return",
@@ -19137,7 +19108,7 @@
     },
     {
       "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/routing/route.ts:2199"
+      "line": " packages/@ember/routing/route.ts:2085"
     },
     {
       "message": "unknown tag: internal",
@@ -19168,48 +19139,52 @@
       "line": " packages/@ember/-internals/glimmer/lib/helpers/-track-array.ts:12"
     },
     {
-      "message": "Missing item type\nNot sure why this is here, we use the owner of the template for lookups.\n\nMaybe this is for the render helper?",
-      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:5"
+      "message": "Missing item type\nThis is usually inherited from the parent (all the way up to the app\ninstance). However, engines uses this to swap out the owner when crossing\na mount point.",
+      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:21"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:28"
     },
     {
-      "message": "Missing item type\nThe name of the parent outlet state.",
-      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:12"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:34"
     },
     {
       "message": "Missing item type\nThe name of the route/template",
-      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:22"
+      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:40"
     },
     {
       "message": "Missing item type\nThe controller (the self of the outlet component)",
-      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:27"
+      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:45"
     },
     {
       "message": "Missing item type\nThe model (the resolved value of the model hook)",
-      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:32"
+      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:50"
     },
     {
       "message": "Missing item type\ntemplate (the layout of the outlet component)",
-      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:37"
+      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:55"
     },
     {
-      "message": "Missing item type\nNested outlet connections.",
-      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:48"
+      "message": "Missing item type\nRepresents what was rendered into this outlet.",
+      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:62"
     },
     {
-      "message": "Missing item type\nRepresents what was rendered into this outlet.",
-      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:53"
+      "message": "Missing item type\nRepresents what, if any, should be rendered into the next {{outlet}} found\nat this level.\n\nThis used to be a dictionary of children outlets, including the {{outlet}}\n\"main\" outlet any {{outlet \"named\"}} named outlets. Since named outlets\nare not a thing anymore, this can now just be a single`child`.",
+      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:67"
     },
     {
-      "message": "Missing item type\nHas to do with render helper and orphan outlets.\nWhether outlet state was rendered.",
-      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:58"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:79"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:118"
+      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:116"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:126"
+      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:124"
     },
     {
       "message": "Missing item type",
@@ -19221,7 +19196,7 @@
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:298"
+      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:299"
     },
     {
       "message": "Missing item type\nThe template-compiler does not support strict mode at this time.\nprecompile from ember-template-compiler returns a string and\nnot a template-factory, so it doesn't help with strict-mode testing.\n\nWe also can't import from `@ember/template-compiler` because it\ndoesn't exist to this kind of test, otherwise we'd be able to use\nprecompileTemplate, which would be perfect :D\n\nCopied(ish) from https://github.com/NullVoxPopuli/ember-repl/blob/main/addon/hbs.ts#L51",
@@ -19649,55 +19624,55 @@
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/core.ts:237"
+      "line": " packages/@ember/object/core.ts:236"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/core.ts:241"
+      "line": " packages/@ember/object/core.ts:240"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:538"
+      "line": " packages/@ember/object/mixin.ts:537"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:541"
+      "line": " packages/@ember/object/mixin.ts:540"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:544"
+      "line": " packages/@ember/object/mixin.ts:543"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:547"
+      "line": " packages/@ember/object/mixin.ts:546"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:550"
+      "line": " packages/@ember/object/mixin.ts:549"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:555"
+      "line": " packages/@ember/object/mixin.ts:554"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:596"
+      "line": " packages/@ember/object/mixin.ts:595"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:653"
+      "line": " packages/@ember/object/mixin.ts:652"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:679"
+      "line": " packages/@ember/object/mixin.ts:678"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:686"
+      "line": " packages/@ember/object/mixin.ts:685"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:693"
+      "line": " packages/@ember/object/mixin.ts:692"
     },
     {
       "message": "Missing item type",
@@ -19721,35 +19696,35 @@
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/routing/route.ts:271"
+      "line": " packages/@ember/routing/route.ts:272"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/routing/route.ts:273"
+      "line": " packages/@ember/routing/route.ts:274"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/routing/route.ts:276"
+      "line": " packages/@ember/routing/route.ts:277"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/routing/route.ts:278"
+      "line": " packages/@ember/routing/route.ts:279"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/routing/route.ts:1597"
+      "line": " packages/@ember/routing/route.ts:1586"
     },
     {
       "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/routing/router.ts:1632"
+      "line": " packages/@ember/routing/router.ts:1623"
     },
     {
       "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/routing/router.ts:1653"
+      "line": " packages/@ember/routing/router.ts:1644"
     },
     {
       "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/routing/router.ts:1675"
+      "line": " packages/@ember/routing/router.ts:1666"
     },
     {
       "message": "Missing item type",