ember-source 6.3.0-alpha.2 → 6.3.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": "6.3.0-alpha.2"
+    "version": "6.3.0-alpha.3"
   },
   "files": {
     "node_modules/rsvp/lib/rsvp/promise/all.js": {
@@ -202,6 +202,13 @@
       },
       "namespaces": {}
     },
+    "packages/@ember/-internals/glimmer/lib/component-managers/route-template.ts": {
+      "name": "packages/@ember/-internals/glimmer/lib/component-managers/route-template.ts",
+      "modules": {},
+      "classes": {},
+      "fors": {},
+      "namespaces": {}
+    },
     "packages/@ember/-internals/glimmer/lib/components/abstract-input.ts": {
       "name": "packages/@ember/-internals/glimmer/lib/components/abstract-input.ts",
       "modules": {},
@@ -2529,7 +2536,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/routing/route.ts",
-      "line": 81
+      "line": 82
     },
     "@ember/routing/router-service": {
       "name": "@ember/routing/router-service",
@@ -4229,7 +4236,7 @@
       "module": "@ember/routing/route",
       "namespace": "",
       "file": "packages/@ember/routing/route.ts",
-      "line": 81,
+      "line": 82,
       "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": [
@@ -5722,6 +5729,13 @@
       "class": "EmberENV",
       "module": "rsvp"
     },
+    {
+      "file": "packages/@ember/-internals/glimmer/lib/component-managers/route-template.ts",
+      "line": 115,
+      "description": "This \"upgrades\" a route template into a invocable component. Conceptually\nit can be 1:1 for each unique `Template`, but it's also cheap to construct,\nso unless the stability is desirable for other reasons, it's probably not\nworth caching this.",
+      "class": "Ember.Templates.helpers",
+      "module": "rsvp"
+    },
     {
       "file": "packages/@ember/-internals/glimmer/lib/components/abstract-input.ts",
       "line": 127,
@@ -6224,7 +6238,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/syntax/outlet.ts",
-      "line": 21,
+      "line": 23,
       "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",
@@ -6291,20 +6305,20 @@
     {
       "file": "packages/@ember/-internals/glimmer/lib/utils/outlet.ts",
       "line": 27,
-      "description": "The template (the route template to use in the {{outlet}})",
+      "description": "The route's template – this is either a Template or a component, and it\ngets normalized during the render process.",
       "class": "@ember/template",
       "module": "ember"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/utils/outlet.ts",
-      "line": 34,
+      "line": 35,
       "description": "Represents what was rendered into this outlet.",
       "class": "@ember/template",
       "module": "ember"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/utils/outlet.ts",
-      "line": 39,
+      "line": 40,
       "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"
@@ -6380,13 +6394,13 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/views/outlet.ts",
-      "line": 114,
+      "line": 113,
       "class": "Component",
       "module": "@ember/template"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/views/outlet.ts",
-      "line": 122,
+      "line": 121,
       "class": "Component",
       "module": "@ember/template"
     },
@@ -6714,7 +6728,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/renderer.ts",
-      "line": 299,
+      "line": 302,
       "class": "Ember.Templates.helpers",
       "module": "@ember/component"
     },
@@ -16051,7 +16065,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 93,
+      "line": 94,
       "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",
@@ -16070,7 +16084,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 138,
+      "line": 139,
       "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",
@@ -16082,7 +16096,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 165,
+      "line": 166,
       "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",
@@ -16106,7 +16120,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 200,
+      "line": 201,
       "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",
@@ -16130,31 +16144,31 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 273,
+      "line": 274,
       "class": "Route",
       "module": "@ember/routing/route"
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 275,
+      "line": 276,
       "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": 280,
+      "line": 281,
       "class": "Route",
       "module": "@ember/routing/route"
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 302,
+      "line": 303,
       "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",
@@ -16182,7 +16196,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 370,
+      "line": 371,
       "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",
@@ -16195,7 +16209,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 423,
+      "line": 424,
       "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",
@@ -16209,7 +16223,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 456,
+      "line": 457,
       "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",
@@ -16223,7 +16237,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 479,
+      "line": 480,
       "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",
@@ -16236,7 +16250,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 510,
+      "line": 511,
       "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",
@@ -16249,7 +16263,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 524,
+      "line": 525,
       "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",
@@ -16262,7 +16276,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 539,
+      "line": 540,
       "description": "Sets the name for this route, including a fully resolved name for routes\ninside engines.",
       "access": "private",
       "tagname": "",
@@ -16280,7 +16294,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 554,
+      "line": 555,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -16290,7 +16304,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 588,
+      "line": 589,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -16300,7 +16314,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 597,
+      "line": 598,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -16310,7 +16324,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 605,
+      "line": 606,
       "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",
@@ -16333,7 +16347,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 686,
+      "line": 687,
       "description": "Serializes the query parameter key",
       "itemtype": "method",
       "name": "serializeQueryParamKey",
@@ -16351,7 +16365,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 697,
+      "line": 698,
       "description": "Serializes value of the query parameter based on defaultValueType",
       "itemtype": "method",
       "name": "serializeQueryParam",
@@ -16379,7 +16393,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 713,
+      "line": 714,
       "description": "Deserializes value of the query parameter based on defaultValueType",
       "itemtype": "method",
       "name": "deserializeQueryParam",
@@ -16407,7 +16421,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 729,
+      "line": 730,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -16417,7 +16431,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 745,
+      "line": 746,
       "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",
@@ -16446,7 +16460,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 775,
+      "line": 776,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -16456,7 +16470,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 786,
+      "line": 787,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -16467,7 +16481,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 800,
+      "line": 801,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -16477,7 +16491,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 811,
+      "line": 812,
       "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",
@@ -16489,7 +16503,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 831,
+      "line": 832,
       "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",
@@ -16501,7 +16515,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 851,
+      "line": 852,
       "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",
@@ -16520,7 +16534,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 862,
+      "line": 863,
       "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",
@@ -16539,7 +16553,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 873,
+      "line": 874,
       "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",
@@ -16563,7 +16577,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 895,
+      "line": 896,
       "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",
@@ -16579,7 +16593,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 921,
+      "line": 922,
       "description": "This hook is the entry point for router.js",
       "access": "private",
       "tagname": "",
@@ -16590,7 +16604,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 996,
+      "line": 997,
       "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",
@@ -16613,7 +16627,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1031,
+      "line": 1032,
       "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",
@@ -16641,7 +16655,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1075,
+      "line": 1076,
       "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",
@@ -16665,7 +16679,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1100,
+      "line": 1101,
       "description": "Called when the context is changed by router.js.",
       "access": "private",
       "tagname": "",
@@ -16676,7 +16690,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1110,
+      "line": 1111,
       "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",
@@ -16704,7 +16718,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1228,
+      "line": 1229,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -16730,7 +16744,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1241,
+      "line": 1242,
       "itemtype": "method",
       "name": "findModel",
       "params": [
@@ -16752,7 +16766,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1265,
+      "line": 1266,
       "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```"
@@ -16785,7 +16799,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1344,
+      "line": 1345,
       "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",
@@ -16808,7 +16822,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1398,
+      "line": 1399,
       "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",
@@ -16826,7 +16840,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1426,
+      "line": 1427,
       "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",
@@ -16849,7 +16863,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1500,
+      "line": 1501,
       "description": "`this[RENDER]` is used to set up the rendering option for the outlet state.",
       "itemtype": "method",
       "name": "this[RENDER]",
@@ -16860,7 +16874,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1514,
+      "line": 1515,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -16870,7 +16884,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1526,
+      "line": 1527,
       "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",
@@ -16885,13 +16899,13 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1577,
+      "line": 1578,
       "class": "Route",
       "module": "@ember/routing/route"
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1626,
+      "line": 1627,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -16901,7 +16915,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1765,
+      "line": 1766,
       "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",
@@ -16925,7 +16939,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 2043,
+      "line": 2096,
       "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",
@@ -16938,7 +16952,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 2074,
+      "line": 2127,
       "description": "This action is called when one or more query params have changed. Bubbles.",
       "itemtype": "method",
       "name": "queryParamsDidChange",
@@ -19486,12 +19500,16 @@
     },
     {
       "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/routing/route.ts:2074"
+      "line": " packages/@ember/routing/route.ts:2127"
     },
     {
       "message": "unknown tag: internal",
       "line": " packages/@ember/runloop/index.ts:88"
     },
+    {
+      "message": "Missing item type\nThis \"upgrades\" a route template into a invocable component. Conceptually\nit can be 1:1 for each unique `Template`, but it's also cheap to construct,\nso unless the stability is desirable for other reasons, it's probably not\nworth caching this.",
+      "line": " packages/@ember/-internals/glimmer/lib/component-managers/route-template.ts:115"
+    },
     {
       "message": "Missing item type\nThe `change` and `input` actions need to be overridden in the `Input`\nsubclass. Unfortunately, some ember-source builds currently uses babel\nloose mode to transpile its classes. Having the `@action` decorator on the\nsuper class creates a getter on the prototype, and when the subclass\noverrides the method, the loose mode transpilation would emit something\nlike `Subclass.prototype['change'] = function change() { ... }`, which\nfails because `prototype['change']` is getter-only/readonly. The correct\nsolution is to use `Object.defineProperty(prototype, 'change', ...)` but\nthat requires disabling loose mode. For now, the workaround is to add the\ndecorator only on the subclass. This is more of a configuration issue on\nour own builds and doesn't really affect apps.",
       "line": " packages/@ember/-internals/glimmer/lib/components/abstract-input.ts:127"
@@ -19533,24 +19551,24 @@
       "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:22"
     },
     {
-      "message": "Missing item type\nThe template (the route template to use in the {{outlet}})",
+      "message": "Missing item type\nThe route's template – this is either a Template or a component, and it\ngets normalized during the render process.",
       "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:27"
     },
     {
       "message": "Missing item type\nRepresents what was rendered into this outlet.",
-      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:34"
+      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:35"
     },
     {
       "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:39"
+      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:40"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:114"
+      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:113"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:122"
+      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:121"
     },
     {
       "message": "Missing item type",
@@ -19562,7 +19580,7 @@
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:299"
+      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:302"
     },
     {
       "message": "Missing item type\nThis function is used to hide a variable from the transpiler, so that it\ndoesn't get removed as \"unused\". It does not actually do anything with the\nvariable, it just makes it be part of an expression that the transpiler\nwon't remove.\n\nIt's a bit of a hack, but it's necessary for testing.",
@@ -20070,23 +20088,23 @@
     },
     {
       "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:275"
+      "line": " packages/@ember/routing/route.ts:276"
     },
     {
       "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:280"
+      "line": " packages/@ember/routing/route.ts:281"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/routing/route.ts:1577"
+      "line": " packages/@ember/routing/route.ts:1578"
     },
     {
       "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`.",