ember-source 4.0.0-beta.5 → 4.0.0-beta.9

package/docs/data.json

@@ -3,7 +3,7 @@
     "name": "The Ember API",
     "description": "The Ember API: a framework for building ambitious web applications",
     "url": "https://emberjs.com/",
-    "version": "4.0.0-beta.5"
+    "version": "4.0.0-beta.9"
   },
   "files": {
     "node_modules/rsvp/lib/rsvp/promise/all.js": {
@@ -220,27 +220,6 @@
       "fors": {},
       "namespaces": {}
     },
-    "packages/@ember/-internals/glimmer/lib/components/-link-to.ts": {
-      "name": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "modules": {},
-      "classes": {
-        "LinkComponent": 1
-      },
-      "fors": {
-        "Ember.Templates.components": 1,
-        "Ember.Templates.helpers": 1
-      },
-      "namespaces": {}
-    },
-    "packages/@ember/-internals/glimmer/lib/components/-textarea.ts": {
-      "name": "packages/@ember/-internals/glimmer/lib/components/-textarea.ts",
-      "modules": {},
-      "classes": {
-        "TextArea": 1
-      },
-      "fors": {},
-      "namespaces": {}
-    },
     "packages/@ember/-internals/glimmer/lib/components/abstract-input.ts": {
       "name": "packages/@ember/-internals/glimmer/lib/components/abstract-input.ts",
       "modules": {},
@@ -248,21 +227,13 @@
       "fors": {},
       "namespaces": {}
     },
-    "packages/@ember/-internals/glimmer/lib/components/checkbox.ts": {
-      "name": "packages/@ember/-internals/glimmer/lib/components/checkbox.ts",
-      "modules": {},
-      "classes": {
-        "Checkbox": 1
-      },
-      "fors": {},
-      "namespaces": {}
-    },
     "packages/@ember/-internals/glimmer/lib/components/input.ts": {
       "name": "packages/@ember/-internals/glimmer/lib/components/input.ts",
       "modules": {},
       "classes": {},
       "fors": {
         "Ember.Templates.helpers": 1,
+        "@ember/component": 1,
         "Ember.Templates.components": 1
       },
       "namespaces": {}
@@ -274,13 +245,15 @@
       "fors": {},
       "namespaces": {}
     },
-    "packages/@ember/-internals/glimmer/lib/components/text-field.ts": {
-      "name": "packages/@ember/-internals/glimmer/lib/components/text-field.ts",
+    "packages/@ember/-internals/glimmer/lib/components/link-to.ts": {
+      "name": "packages/@ember/-internals/glimmer/lib/components/link-to.ts",
       "modules": {},
-      "classes": {
-        "TextField": 1
+      "classes": {},
+      "fors": {
+        "Ember.Templates.components": 1,
+        "Ember.Templates.helpers": 1,
+        "@ember/routing": 1
       },
-      "fors": {},
       "namespaces": {}
     },
     "packages/@ember/-internals/glimmer/lib/components/textarea.ts": {
@@ -289,7 +262,8 @@
       "classes": {},
       "fors": {
         "Ember.Templates.components": 1,
-        "Ember.Templates.helpers": 1
+        "Ember.Templates.helpers": 1,
+        "@ember/component": 1
       },
       "namespaces": {}
     },
@@ -422,15 +396,6 @@
       },
       "namespaces": {}
     },
-    "packages/@ember/-internals/glimmer/lib/helpers/query-param.ts": {
-      "name": "packages/@ember/-internals/glimmer/lib/helpers/query-param.ts",
-      "modules": {},
-      "classes": {},
-      "fors": {
-        "Ember.Templates.helpers": 1
-      },
-      "namespaces": {}
-    },
     "packages/@ember/-internals/glimmer/lib/helpers/readonly.ts": {
       "name": "packages/@ember/-internals/glimmer/lib/helpers/readonly.ts",
       "modules": {},
@@ -1268,17 +1233,6 @@
         "Ember": 1
       }
     },
-    "packages/@ember/-internals/views/lib/mixins/text_support.js": {
-      "name": "packages/@ember/-internals/views/lib/mixins/text_support.js",
-      "modules": {},
-      "classes": {
-        "Ember.TextSupport": 1
-      },
-      "fors": {},
-      "namespaces": {
-        "Ember": 1
-      }
-    },
     "packages/@ember/-internals/views/lib/mixins/view_state_support.js": {
       "name": "packages/@ember/-internals/views/lib/mixins/view_state_support.js",
       "modules": {},
@@ -1789,6 +1743,56 @@
       "access": "public",
       "tagname": ""
     },
+    "@ember/component": {
+      "name": "@ember/component",
+      "submodules": {},
+      "elements": {},
+      "classes": {
+        "@ember/component": 1,
+        "Component": 1,
+        "Helper": 1,
+        "@ember/component/helper": 1
+      },
+      "fors": {
+        "Ember.Templates.helpers": 1,
+        "@ember/component": 1,
+        "Ember.Templates.components": 1,
+        "@ember/component/helper": 1
+      },
+      "namespaces": {},
+      "tag": "main",
+      "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
+      "line": 34,
+      "description": "[Glimmer](https://github.com/tildeio/glimmer) is a templating engine used by Ember.js that is compatible with a subset of the [Handlebars](http://handlebarsjs.com/) syntax.\n\n### Showing a property\n\nTemplates manage the flow of an application's UI, and display state (through\nthe DOM) to a user. For example, given a component with the property \"name\",\nthat component's template can use the name in several ways:\n\n```app/components/person-profile.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  name: 'Jill'\n});\n```\n\n```app/components/person-profile.hbs\n{{this.name}}\n<div>{{this.name}}</div>\n<span data-name={{this.name}}></span>\n```\n\nAny time the \"name\" property on the component changes, the DOM will be\nupdated.\n\nProperties can be chained as well:\n\n```handlebars\n{{@aUserModel.name}}\n<div>{{@listOfUsers.firstObject.name}}</div>\n```\n\n### Using Ember helpers\n\nWhen content is passed in mustaches `{{}}`, Ember will first try to find a helper\nor component with that name. For example, the `if` helper:\n\n```app/components/person-profile.hbs\n{{if this.name \"I have a name\" \"I have no name\"}}\n<span data-has-name={{if this.name true}}></span>\n```\n\nThe returned value is placed where the `{{}}` is called. The above style is\ncalled \"inline\". A second style of helper usage is called \"block\". For example:\n\n```handlebars\n{{#if this.name}}\n  I have a name\n{{else}}\n  I have no name\n{{/if}}\n```\n\nThe block form of helpers allows you to control how the UI is created based\non the values of properties.\nA third form of helper is called \"nested\". For example here the concat\nhelper will add \" Doe\" to a displayed name if the person has no last name:\n\n```handlebars\n<span data-name={{concat this.firstName (\n  if this.lastName (concat \" \" this.lastName) \"Doe\"\n)}}></span>\n```\n\nEmber's built-in helpers are described under the [Ember.Templates.helpers](/ember/release/classes/Ember.Templates.helpers)\nnamespace. Documentation on creating custom helpers can be found under\n[helper](/ember/release/functions/@ember%2Fcomponent%2Fhelper/helper) (or\nunder [Helper](/ember/release/classes/Helper) if a helper requires access to\ndependency injection).\n\n### Invoking a Component\n\nEmber components represent state to the UI of an application. Further\nreading on components can be found under [Component](/ember/release/classes/Component).",
+      "itemtype": "main"
+    },
+    "@ember/routing": {
+      "name": "@ember/routing",
+      "submodules": {},
+      "elements": {},
+      "classes": {
+        "Ember.Templates.components": 1,
+        "@ember/routing": 1,
+        "Location": 1,
+        "AutoLocation": 1,
+        "HashLocation": 1,
+        "HistoryLocation": 1,
+        "NoneLocation": 1,
+        "RouterService": 1,
+        "Route": 1,
+        "EmberRouter": 1,
+        "Transition": 1
+      },
+      "fors": {
+        "Ember.Templates.helpers": 1,
+        "@ember/routing": 1,
+        "Route": 1
+      },
+      "namespaces": {},
+      "tag": "module",
+      "file": "packages/@ember/-internals/routing/lib/system/transition.ts",
+      "line": 1
+    },
     "ember": {
       "name": "ember",
       "submodules": {},
@@ -1815,7 +1819,6 @@
         "Ember.Namespace": 1,
         "Ember.ActionSupport": 1,
         "Ember.ClassNamesSupport": 1,
-        "Ember.TextSupport": 1,
         "Ember.ViewMixin": 1,
         "Ember.EventDispatcher": 1,
         "Ember.CoreView": 1,
@@ -1823,7 +1826,6 @@
         "Ember.Test": 1
       },
       "fors": {
-        "Ember.Templates.components": 1,
         "Ember.Templates.helpers": 1,
         "Ember": 1,
         "@ember/object": 1,
@@ -1840,56 +1842,6 @@
       "access": "private",
       "tagname": ""
     },
-    "@ember/routing": {
-      "name": "@ember/routing",
-      "submodules": {},
-      "elements": {},
-      "classes": {
-        "Ember.Templates.components": 1,
-        "LinkComponent": 1,
-        "Location": 1,
-        "AutoLocation": 1,
-        "HashLocation": 1,
-        "HistoryLocation": 1,
-        "NoneLocation": 1,
-        "RouterService": 1,
-        "Route": 1,
-        "EmberRouter": 1,
-        "Transition": 1
-      },
-      "fors": {
-        "Ember.Templates.helpers": 1,
-        "Route": 1
-      },
-      "namespaces": {},
-      "tag": "module",
-      "file": "packages/@ember/-internals/routing/lib/system/transition.ts",
-      "line": 1
-    },
-    "@ember/component": {
-      "name": "@ember/component",
-      "submodules": {},
-      "elements": {},
-      "classes": {
-        "TextArea": 1,
-        "Checkbox": 1,
-        "TextField": 1,
-        "Component": 1,
-        "Helper": 1,
-        "@ember/component/helper": 1
-      },
-      "fors": {
-        "Ember.Templates.helpers": 1,
-        "Ember.Templates.components": 1,
-        "@ember/component/helper": 1
-      },
-      "namespaces": {},
-      "tag": "main",
-      "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
-      "line": 40,
-      "description": "[Glimmer](https://github.com/tildeio/glimmer) is a templating engine used by Ember.js that is compatible with a subset of the [Handlebars](http://handlebarsjs.com/) syntax.\n\n### Showing a property\n\nTemplates manage the flow of an application's UI, and display state (through\nthe DOM) to a user. For example, given a component with the property \"name\",\nthat component's template can use the name in several ways:\n\n```app/components/person-profile.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  name: 'Jill'\n});\n```\n\n```app/components/person-profile.hbs\n{{this.name}}\n<div>{{this.name}}</div>\n<span data-name={{this.name}}></span>\n```\n\nAny time the \"name\" property on the component changes, the DOM will be\nupdated.\n\nProperties can be chained as well:\n\n```handlebars\n{{@aUserModel.name}}\n<div>{{@listOfUsers.firstObject.name}}</div>\n```\n\n### Using Ember helpers\n\nWhen content is passed in mustaches `{{}}`, Ember will first try to find a helper\nor component with that name. For example, the `if` helper:\n\n```app/components/person-profile.hbs\n{{if this.name \"I have a name\" \"I have no name\"}}\n<span data-has-name={{if this.name true}}></span>\n```\n\nThe returned value is placed where the `{{}}` is called. The above style is\ncalled \"inline\". A second style of helper usage is called \"block\". For example:\n\n```handlebars\n{{#if this.name}}\n  I have a name\n{{else}}\n  I have no name\n{{/if}}\n```\n\nThe block form of helpers allows you to control how the UI is created based\non the values of properties.\nA third form of helper is called \"nested\". For example here the concat\nhelper will add \" Doe\" to a displayed name if the person has no last name:\n\n```handlebars\n<span data-name={{concat this.firstName (\n  if this.lastName (concat \" \" this.lastName) \"Doe\"\n)}}></span>\n```\n\nEmber's built-in helpers are described under the [Ember.Templates.helpers](/ember/release/classes/Ember.Templates.helpers)\nnamespace. Documentation on creating custom helpers can be found under\n[helper](/ember/release/functions/@ember%2Fcomponent%2Fhelper/helper) (or\nunder [Helper](/ember/release/classes/Helper) if a helper requires access to\ndependency injection).\n\n### Invoking a Component\n\nEmber components represent state to the UI of an application. Further\nreading on components can be found under [Component](/ember/release/classes/Component).",
-      "itemtype": "main"
-    },
     "@ember/template": {
       "name": "@ember/template",
       "submodules": {},
@@ -2077,7 +2029,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/canary-features/index.ts",
-      "line": 26,
+      "line": 25,
       "description": "Set `EmberENV.FEATURES` in your application's `config/environment.js` file\nto enable canary features in your application.\n\nSee the [feature flag guide](https://guides.emberjs.com/release/configuring-ember/feature-flags/)\nfor more details.",
       "access": "public",
       "tagname": ""
@@ -2420,17 +2372,6 @@
       "access": "public",
       "tagname": ""
     },
-    "Ember.Templates.components": {
-      "name": "Ember.Templates.components",
-      "shortname": "Ember.Templates.components",
-      "classitems": [],
-      "plugins": [],
-      "extensions": [],
-      "plugin_for": [],
-      "extension_for": [],
-      "module": "@ember/routing",
-      "namespace": ""
-    },
     "Ember.Templates.helpers": {
       "name": "Ember.Templates.helpers",
       "shortname": "Ember.Templates.helpers",
@@ -2446,85 +2387,38 @@
       "access": "public",
       "tagname": ""
     },
-    "LinkComponent": {
-      "name": "LinkComponent",
-      "shortname": "LinkComponent",
-      "classitems": [],
-      "plugins": [],
-      "extensions": [],
-      "plugin_for": [],
-      "extension_for": [],
-      "module": "@ember/routing",
-      "namespace": "",
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 263,
-      "description": "`LinkComponent` is the internal component invoked with `<LinkTo>` or `{{link-to}}`.",
-      "extends": "Component",
-      "see": [
-        "{Ember.Templates.components.LinkTo}"
-      ],
-      "access": "public",
-      "tagname": ""
-    },
-    "TextArea": {
-      "name": "TextArea",
-      "shortname": "TextArea",
+    "@ember/component": {
+      "name": "@ember/component",
+      "shortname": "@ember/component",
       "classitems": [],
       "plugins": [],
       "extensions": [],
       "plugin_for": [],
       "extension_for": [],
       "module": "@ember/component",
-      "namespace": "",
-      "file": "packages/@ember/-internals/glimmer/lib/components/-textarea.ts",
-      "line": 11,
-      "description": "The internal representation used for `Textarea` invocations.",
-      "extends": "Component",
-      "see": [
-        "{Ember.Templates.components.Textarea}"
-      ],
-      "uses": [
-        "Ember.TextSupport"
-      ],
-      "access": "public",
-      "tagname": ""
+      "namespace": ""
     },
-    "Checkbox": {
-      "name": "Checkbox",
-      "shortname": "Checkbox",
+    "Ember.Templates.components": {
+      "name": "Ember.Templates.components",
+      "shortname": "Ember.Templates.components",
       "classitems": [],
       "plugins": [],
       "extensions": [],
       "plugin_for": [],
       "extension_for": [],
-      "module": "@ember/component",
-      "namespace": "",
-      "file": "packages/@ember/-internals/glimmer/lib/components/checkbox.ts",
-      "line": 13,
-      "description": "The internal class used to create text inputs when the `{{input}}`\nhelper is used with `type` of `checkbox`.\n\nSee [Ember.Templates.helpers.input](/ember/release/classes/Ember.Templates.helpers/methods/input?anchor=input)  for usage details.\n\n## Direct manipulation of `checked`\n\nThe `checked` attribute of an `Checkbox` object should always be set\nthrough the Ember object or by interacting with its rendered element\nrepresentation via the mouse, keyboard, or touch. Updating the value of the\ncheckbox via jQuery will result in the checked value of the object and its\nelement losing synchronization.\n\n## Layout and LayoutName properties\n\nBecause HTML `input` elements are self closing `layout` and `layoutName`\nproperties will not be applied.",
-      "extends": "Component",
-      "access": "public",
-      "tagname": ""
+      "module": "@ember/routing",
+      "namespace": ""
     },
-    "TextField": {
-      "name": "TextField",
-      "shortname": "TextField",
+    "@ember/routing": {
+      "name": "@ember/routing",
+      "shortname": "@ember/routing",
       "classitems": [],
       "plugins": [],
       "extensions": [],
       "plugin_for": [],
       "extension_for": [],
-      "module": "@ember/component",
-      "namespace": "",
-      "file": "packages/@ember/-internals/glimmer/lib/components/text-field.ts",
-      "line": 36,
-      "description": "The internal class used to create text inputs when the `Input` component is used with `type` of `text`.\n\nSee [Ember.Templates.components.Input](/ember/release/classes/Ember.Templates.components/methods/Input?anchor=Input) for usage details.\n\n## Layout and LayoutName properties\n\nBecause HTML `input` elements are self closing `layout` and `layoutName`\nproperties will not be applied.",
-      "extends": "Component",
-      "uses": [
-        "Ember.TextSupport"
-      ],
-      "access": "public",
-      "tagname": ""
+      "module": "@ember/routing",
+      "namespace": ""
     },
     "ComponentStateBucket": {
       "name": "ComponentStateBucket",
@@ -2564,7 +2458,7 @@
       "module": "@ember/component",
       "namespace": "",
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 38,
+      "line": 37,
       "description": "A component is a reusable UI element that consists of a `.hbs` template and an\noptional JavaScript class that defines its behavior. For example, someone\nmight make a `button` in the template and handle the click behavior in the\nJavaScript file that shares the same name as the template.\n\nComponents are broken down into two categories:\n\n- Components _without_ JavaScript, that are based only on a template. These\n  are called Template-only or TO components.\n- Components _with_ JavaScript, which consist of a template and a backing\n  class.\n\nEmber ships with two types of JavaScript classes for components:\n\n1. Glimmer components, imported from `@glimmer/component`, which are the\n   default component's for Ember Octane (3.15) and more recent editions.\n2. Classic components, imported from `@ember/component`, which were the\n   default for older editions of Ember (pre 3.15).\n\nBelow is the documentation for Classic components. If you are looking for the\nAPI documentation for Template-only or Glimmer components, it is\n[available here](/ember/release/modules/@glimmer%2Fcomponent).\n\n## Defining a Classic Component\n\nIf you want to customize the component in order to handle events, transform\narguments or maintain internal state, you implement a subclass of `Component`.\n\nOne example is to add computed properties to your component:\n\n```app/components/person-profile.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  displayName: computed('person.title', 'person.firstName', 'person.lastName', function() {\n    let { title, firstName, lastName } = this.person;\n\n    if (title) {\n      return `${title} ${lastName}`;\n    } else {\n      return `${firstName} ${lastName}`;\n    }\n  })\n});\n```\n\nAnd then use it in the component's template:\n\n```app/templates/components/person-profile.hbs\n<h1>{{this.displayName}}</h1>\n{{yield}}\n```\n\n## Customizing a Classic Component's HTML Element in JavaScript\n\n### HTML Tag\n\nThe default HTML tag name used for a component's HTML representation is `div`.\nThis can be customized by setting the `tagName` property.\n\nConsider the following component class:\n\n```app/components/emphasized-paragraph.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  tagName: 'em'\n});\n```\n\nWhen invoked, this component would produce output that looks something like\nthis:\n\n```html\n<em id=\"ember1\" class=\"ember-view\"></em>\n```\n\n### HTML `class` Attribute\n\nThe HTML `class` attribute of a component's tag can be set by providing a\n`classNames` property that is set to an array of strings:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  classNames: ['my-class', 'my-other-class']\n});\n```\n\nInvoking this component will produce output that looks like this:\n\n```html\n<div id=\"ember1\" class=\"ember-view my-class my-other-class\"></div>\n```\n\n`class` attribute values can also be set by providing a `classNameBindings`\nproperty set to an array of properties names for the component. The return\nvalue of these properties will be added as part of the value for the\ncomponents's `class` attribute. These properties can be computed properties:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\nimport { computed } from '@ember/object';\n\nexport default Component.extend({\n  classNames: ['my-class', 'my-other-class'],\n  classNameBindings: ['propertyA', 'propertyB'],\n\n  propertyA: 'from-a',\n  propertyB: computed(function() {\n    if (someLogic) { return 'from-b'; }\n  })\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view my-class my-other-class from-a from-b\"></div>\n```\n\nNote that `classNames` and `classNameBindings` is in addition to the `class`\nattribute passed with the angle bracket invocation syntax. Therefore, if this\ncomponent was invoked like so:\n\n```handlebars\n<MyWidget class=\"from-invocation\" />\n```\n\nThe resulting HTML will look similar to this:\n\n```html\n<div id=\"ember1\" class=\"from-invocation ember-view my-class my-other-class from-a from-b\"></div>\n```\n\nIf the value of a class name binding returns a boolean the property name\nitself will be used as the class name if the property is true. The class name\nwill not be added if the value is `false` or `undefined`.\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  classNameBindings: ['hovered'],\n\n  hovered: true\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view hovered\"></div>\n```\n\n### Custom Class Names for Boolean Values\n\nWhen using boolean class name bindings you can supply a string value other\nthan the property name for use as the `class` HTML attribute by appending the\npreferred value after a \":\" character when defining the binding:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  classNameBindings: ['awesome:so-very-cool'],\n\n  awesome: true\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view so-very-cool\"></div>\n```\n\nBoolean value class name bindings whose property names are in a\ncamelCase-style format will be converted to a dasherized format:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  classNameBindings: ['isUrgent'],\n\n  isUrgent: true\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view is-urgent\"></div>\n```\n\nClass name bindings can also refer to object values that are found by\ntraversing a path relative to the component itself:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\nimport EmberObject from '@ember/object';\n\nexport default Component.extend({\n  classNameBindings: ['messages.empty'],\n\n  messages: EmberObject.create({\n    empty: true\n  })\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view empty\"></div>\n```\n\nIf you want to add a class name for a property which evaluates to true and\nand a different class name if it evaluates to false, you can pass a binding\nlike this:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  classNameBindings: ['isEnabled:enabled:disabled'],\n  isEnabled: true\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view enabled\"></div>\n```\n\nWhen isEnabled is `false`, the resulting HTML representation looks like this:\n\n```html\n<div id=\"ember1\" class=\"ember-view disabled\"></div>\n```\n\nThis syntax offers the convenience to add a class if a property is `false`:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\n// Applies no class when isEnabled is true and class 'disabled' when isEnabled is false\nexport default Component.extend({\n  classNameBindings: ['isEnabled::disabled'],\n  isEnabled: true\n});\n```\n\nInvoking this component when the `isEnabled` property is true will produce\nHTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view\"></div>\n```\n\nInvoking it when the `isEnabled` property on the component is `false` will\nproduce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view disabled\"></div>\n```\n\nUpdates to the value of a class name binding will result in automatic update\nof the  HTML `class` attribute in the component's rendered HTML\nrepresentation. If the value becomes `false` or `undefined` the class name\nwill be removed.\n\nBoth `classNames` and `classNameBindings` are concatenated properties. See\n[EmberObject](/ember/release/classes/EmberObject) documentation for more\ninformation about concatenated properties.\n\n### Other HTML Attributes\n\nThe HTML attribute section of a component's tag can be set by providing an\n`attributeBindings` property set to an array of property names on the component.\nThe return value of these properties will be used as the value of the component's\nHTML associated attribute:\n\n```app/components/my-anchor.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  tagName: 'a',\n  attributeBindings: ['href'],\n\n  href: 'http://google.com'\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<a id=\"ember1\" class=\"ember-view\" href=\"http://google.com\"></a>\n```\n\nOne property can be mapped on to another by placing a \":\" between\nthe source property and the destination property:\n\n```app/components/my-anchor.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  tagName: 'a',\n  attributeBindings: ['url:href'],\n\n  url: 'http://google.com'\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<a id=\"ember1\" class=\"ember-view\" href=\"http://google.com\"></a>\n```\n\nHTML attributes passed with angle bracket invocations will take precedence\nover those specified in `attributeBindings`. Therefore, if this component was\ninvoked like so:\n\n```handlebars\n<MyAnchor href=\"http://bing.com\" @url=\"http://google.com\" />\n```\n\nThe resulting HTML will looks like this:\n\n```html\n<a id=\"ember1\" class=\"ember-view\" href=\"http://bing.com\"></a>\n```\n\nNote that the `href` attribute is ultimately set to `http://bing.com`,\ndespite it having attribute binidng to the `url` property, which was\nset to `http://google.com`.\n\nNamespaced attributes (e.g. `xlink:href`) are supported, but have to be\nmapped, since `:` is not a valid character for properties in Javascript:\n\n```app/components/my-use.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  tagName: 'use',\n  attributeBindings: ['xlinkHref:xlink:href'],\n\n  xlinkHref: '#triangle'\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<use xlink:href=\"#triangle\"></use>\n```\n\nIf the value of a property monitored by `attributeBindings` is a boolean, the\nattribute will be present or absent depending on the value:\n\n```app/components/my-text-input.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  tagName: 'input',\n  attributeBindings: ['disabled'],\n\n  disabled: false\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<input id=\"ember1\" class=\"ember-view\" />\n```\n\n`attributeBindings` can refer to computed properties:\n\n```app/components/my-text-input.js\nimport Component from '@ember/component';\nimport { computed } from '@ember/object';\n\nexport default Component.extend({\n  tagName: 'input',\n  attributeBindings: ['disabled'],\n\n  disabled: computed(function() {\n    if (someLogic) {\n      return true;\n    } else {\n      return false;\n    }\n  })\n});\n```\n\nTo prevent setting an attribute altogether, use `null` or `undefined` as the\nvalue of the property used in `attributeBindings`:\n\n```app/components/my-text-input.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  tagName: 'form',\n  attributeBindings: ['novalidate'],\n  novalidate: null\n});\n```\n\nUpdates to the property of an attribute binding will result in automatic\nupdate of the  HTML attribute in the component's HTML output.\n\n`attributeBindings` is a concatenated property. See\n[EmberObject](/ember/release/classes/EmberObject) documentation for more\ninformation about concatenated properties.\n\n## Layouts\n\nThe `layout` property can be used to dynamically specify a template associated\nwith a component class, instead of relying on Ember to link together a\ncomponent class and a template based on file names.\n\nIn general, applications should not use this feature, but it's commonly used\nin addons for historical reasons.\n\nThe `layout` property should be set to the default export of a template\nmodule, which is the name of a template file without the `.hbs` extension.\n\n```app/templates/components/person-profile.hbs\n<h1>Person's Title</h1>\n<div class='details'>{{yield}}</div>\n```\n\n```app/components/person-profile.js\n  import Component from '@ember/component';\n  import layout from '../templates/components/person-profile';\n\n  export default Component.extend({\n    layout\n  });\n```\n\nIf you invoke the component:\n\n```handlebars\n<PersonProfile>\n  <h2>Chief Basket Weaver</h2>\n  <h3>Fisherman Industries</h3>\n</PersonProfile>\n```\n\nor\n\n```handlebars\n{{#person-profile}}\n  <h2>Chief Basket Weaver</h2>\n  <h3>Fisherman Industries</h3>\n{{/person-profile}}\n```\n\nIt will result in the following HTML output:\n\n```html\n<h1>Person's Title</h1>\n  <div class=\"details\">\n  <h2>Chief Basket Weaver</h2>\n  <h3>Fisherman Industries</h3>\n</div>\n```\n\n## Handling Browser Events\n\nComponents can respond to user-initiated events in one of three ways: passing\nactions with angle bracket invocation, adding event handler methods to the\ncomponent's class, or adding actions to the component's template.\n\n### Passing Actions With Angle Bracket Invocation\n\nFor one-off events specific to particular instance of a component, it is possible\nto pass actions to the component's element using angle bracket invocation syntax.\n\n```handlebars\n<MyWidget {{action 'firstWidgetClicked'}} />\n\n<MyWidget {{action 'secondWidgetClicked'}} />\n```\n\nIn this case, when the first component is clicked on, Ember will invoke the\n`firstWidgetClicked` action. When the second component is clicked on, Ember\nwill invoke the `secondWidgetClicked` action instead.\n\nBesides `{{action}}`, it is also possible to pass any arbitrary element modifiers\nusing the angle bracket invocation syntax.\n\n### Event Handler Methods\n\nComponents can also respond to user-initiated events by implementing a method\nthat matches the event name. This approach is appropriate when the same event\nshould be handled by all instances of the same component.\n\nAn event object will be passed as the argument to the event handler method.\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  click(event) {\n    // `event.target` is either the component's element or one of its children\n    let tag = event.target.tagName.toLowerCase();\n    console.log('clicked on a `<${tag}>` HTML element!');\n  }\n});\n```\n\nIn this example, whenever the user clicked anywhere inside the component, it\nwill log a message to the console.\n\nIt is possible to handle event types other than `click` by implementing the\nfollowing event handler methods. In addition, custom events can be registered\nby using `Application.customEvents`.\n\nTouch events:\n\n* `touchStart`\n* `touchMove`\n* `touchEnd`\n* `touchCancel`\n\nKeyboard events:\n\n* `keyDown`\n* `keyUp`\n* `keyPress`\n\nMouse events:\n\n* `mouseDown`\n* `mouseUp`\n* `contextMenu`\n* `click`\n* `doubleClick`\n* `focusIn`\n* `focusOut`\n\nForm events:\n\n* `submit`\n* `change`\n* `focusIn`\n* `focusOut`\n* `input`\n\nDrag and drop events:\n\n* `dragStart`\n* `drag`\n* `dragEnter`\n* `dragLeave`\n* `dragOver`\n* `dragEnd`\n* `drop`\n\n### `{{action}}` Helper\n\nInstead of handling all events of a particular type anywhere inside the\ncomponent's element, you may instead want to limit it to a particular\nelement in the component's template. In this case, it would be more\nconvenient to implement an action instead.\n\nFor example, you could implement the action `hello` for the `person-profile`\ncomponent:\n\n```app/components/person-profile.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  actions: {\n    hello(name) {\n      console.log(\"Hello\", name);\n    }\n  }\n});\n```\n\nAnd then use it in the component's template:\n\n```app/templates/components/person-profile.hbs\n<h1>{{@person.name}}</h1>\n\n<button {{action 'hello' @person.name}}>\n  Say Hello to {{@person.name}}\n</button>\n```\n\nWhen the user clicks the button, Ember will invoke the `hello` action,\npassing in the current value of `@person.name` as an argument.\n\nSee [Ember.Templates.helpers.action](/ember/release/classes/Ember.Templates.helpers/methods/action?anchor=action).",
       "extends": "Ember.CoreView",
       "uses": [
@@ -2599,7 +2493,7 @@
       "module": "@ember/component",
       "namespace": "",
       "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
-      "line": 40,
+      "line": 34,
       "description": "Ember Helpers are functions that can compute values, and are used in templates.\nFor example, this code calls a helper named `format-currency`:\n\n```app/templates/application.hbs\n<Cost @cents={{230}} />\n```\n\n```app/components/cost.hbs\n<div>{{format-currency @cents currency=\"$\"}}</div>\n```\n\nAdditionally a helper can be called as a nested helper.\nIn this example, we show the formatted currency value if the `showMoney`\nnamed argument is truthy.\n\n```handlebars\n{{if @showMoney (format-currency @cents currency=\"$\")}}\n```\n\nHelpers defined using a class must provide a `compute` function. For example:\n\n```app/helpers/format-currency.js\nimport Helper from '@ember/component/helper';\n\nexport default class extends Helper {\n  compute([cents], { currency }) {\n    return `${currency}${cents * 0.01}`;\n  }\n}\n```\n\nEach time the input to a helper changes, the `compute` function will be\ncalled again.\n\nAs instances, these helpers also have access to the container and will accept\ninjected dependencies.\n\nAdditionally, class helpers can call `recompute` to force a new computation.",
       "extends": "CoreObject",
       "access": "public",
@@ -2794,7 +2688,7 @@
       "module": "@ember/object",
       "namespace": "",
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 445,
+      "line": 444,
       "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": ""
@@ -2965,7 +2859,7 @@
       "namespace": "",
       "file": "packages/@ember/-internals/routing/lib/services/routing.ts",
       "line": 14,
-      "description": "The Routing service is used by LinkComponent, and provides facilities for\nthe component/view layer to interact with the router.\n\nThis is a private service for internal usage only. For public usage,\nrefer to the `Router` service.",
+      "description": "The Routing service is used by LinkTo, and provides facilities for\nthe component/view layer to interact with the router.\n\nThis is a private service for internal usage only. For public usage,\nrefer to the `Router` service.",
       "access": "private",
       "tagname": ""
     },
@@ -3028,7 +2922,7 @@
       "module": "@ember/routing",
       "namespace": "",
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 86,
+      "line": 85,
       "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": [
@@ -3050,7 +2944,7 @@
       "module": "@ember/routing",
       "namespace": "",
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 135,
+      "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": [
@@ -3343,13 +3237,12 @@
       "extensions": [],
       "plugin_for": [],
       "extension_for": [
-        "Component",
-        "Ember.TextSupport"
+        "Component"
       ],
       "module": "ember",
       "namespace": "Ember",
       "file": "packages/@ember/-internals/runtime/lib/mixins/target_action_support.js",
-      "line": 15,
+      "line": 10,
       "description": "`Ember.TargetActionSupport` is a mixin that can be included in a class\nto add a `triggerAction` method with semantics similar to the Handlebars\n`{{action}}` helper. In normal Ember usage, the `{{action}}` helper is\nusually the best choice. This mixin is most often useful when you are\ndoing more complex event handling in Components.",
       "extends": "Mixin",
       "access": "private",
@@ -3493,29 +3386,6 @@
       "access": "private",
       "tagname": ""
     },
-    "Ember.TextSupport": {
-      "name": "Ember.TextSupport",
-      "shortname": "Ember.TextSupport",
-      "classitems": [],
-      "plugins": [],
-      "extensions": [],
-      "plugin_for": [],
-      "extension_for": [
-        "TextArea",
-        "TextField"
-      ],
-      "module": "ember",
-      "namespace": "Ember",
-      "file": "packages/@ember/-internals/views/lib/mixins/text_support.js",
-      "line": 20,
-      "description": "`TextSupport` is a shared mixin used by both `TextField` and\n`TextArea`. `TextSupport` adds a number of methods that allow you to\nspecify a controller action to invoke when a certain event is fired on your\ntext field or textarea. The specified controller action would get the current\nvalue of the field passed in as the only argument unless the value of\nthe field is empty. In that case, the instance of the field itself is passed\nin as the only argument.\n\nLet's use the pressing of the escape key as an example. If you wanted to\ninvoke a controller action when a user presses the escape key while on your\nfield, you would use the `escape-press` attribute on your field like so:\n\n```handlebars\n  {{! application.hbs}}\n\n  {{input escape-press='alertUser'}}\n```\n\n```javascript\n    import Application from '@ember/application';\n    import Controller from '@ember/controller';\n    App = Application.create();\n\n    App.ApplicationController = Controller.extend({\n      actions: {\n        alertUser: function ( currentValue ) {\n          alert( 'escape pressed, current value: ' + currentValue );\n        }\n      }\n    });\n```\n\nThe following chart is a visual representation of what takes place when the\nescape key is pressed in this scenario:\n\n```\nThe Template\n+---------------------------+\n|                           |\n| escape-press='alertUser'  |\n|                           |          TextSupport Mixin\n+----+----------------------+          +-------------------------------+\n     |                                 | cancel method                 |\n     |      escape button pressed      |                               |\n     +-------------------------------> | checks for the `escape-press` |\n                                       | attribute and pulls out the   |\n     +-------------------------------+ | `alertUser` value             |\n     |     action name 'alertUser'     +-------------------------------+\n     |     sent to controller\n     v\nController\n+------------------------------------------ +\n|                                           |\n|  actions: {                               |\n|     alertUser: function( currentValue ){  |\n|       alert( 'the esc key was pressed!' ) |\n|     }                                     |\n|  }                                        |\n|                                           |\n+-------------------------------------------+\n```\n\nHere are the events that we currently support along with the name of the\nattribute you would need to use on your field. To reiterate, you would use the\nattribute name like so:\n\n```handlebars\n  {{input attribute-name='controllerAction'}}\n```\n\n```\n+--------------------+----------------+\n|                    |                |\n| event              | attribute name |\n+--------------------+----------------+\n| new line inserted  | insert-newline |\n|                    |                |\n| enter key pressed  | enter          |\n|                    |                |\n| cancel key pressed | escape-press   |\n|                    |                |\n| focusin            | focus-in       |\n|                    |                |\n| focusout           | focus-out      |\n|                    |                |\n| keypress           | key-press      |\n|                    |                |\n| keyup              | key-up         |\n|                    |                |\n| keydown            | key-down       |\n+--------------------+----------------+\n```",
-      "uses": [
-        "Ember.TargetActionSupport"
-      ],
-      "extends": "Mixin",
-      "access": "private",
-      "tagname": ""
-    },
     "Ember.ViewMixin": {
       "name": "Ember.ViewMixin",
       "shortname": "Ember.ViewMixin",
@@ -3585,7 +3455,7 @@
       "namespace": "",
       "file": "packages/@ember/application/lib/application.js",
       "line": 30,
-      "description": "An instance of `Application` is the starting point for every Ember\napplication. It instantiates, initializes and coordinates the\nobjects that make up your app.\n\nEach Ember app has one and only one `Application` object. Although\nEmber CLI creates this object implicitly, the `Application` class\nis defined in the `app/app.js`. You can define a `ready` method on the\n`Application` class, which will be run by Ember when the application is\ninitialized.\n\n```app/app.js\nconst App = Application.extend({\n  ready() {\n    // your code here\n  }\n})\n```\n\nBecause `Application` ultimately inherits from `Ember.Namespace`, any classes\nyou create will have useful string representations when calling `toString()`.\nSee the `Ember.Namespace` documentation for more information.\n\nWhile you can think of your `Application` as a container that holds the\nother classes in your application, there are several other responsibilities\ngoing on under-the-hood that you may want to understand. It is also important\nto understand that an `Application` is different from an `ApplicationInstance`.\nRefer to the Guides to understand the difference between these.\n\n### Event Delegation\n\nEmber uses a technique called _event delegation_. This allows the framework\nto set up a global, shared event listener instead of requiring each view to\ndo it manually. For example, instead of each view registering its own\n`mousedown` listener on its associated element, Ember sets up a `mousedown`\nlistener on the `body`.\n\nIf a `mousedown` event occurs, Ember will look at the target of the event and\nstart walking up the DOM node tree, finding corresponding views and invoking\ntheir `mouseDown` method as it goes.\n\n`Application` has a number of default events that it listens for, as\nwell as a mapping from lowercase events to camel-cased view method names. For\nexample, the `keypress` event causes the `keyPress` method on the view to be\ncalled, the `dblclick` event causes `doubleClick` to be called, and so on.\n\nIf there is a bubbling browser event that Ember does not listen for by\ndefault, you can specify custom events and their corresponding view method\nnames by setting the application's `customEvents` property:\n\n```app/app.js\nimport Application from '@ember/application';\n\nlet App = Application.extend({\n  customEvents: {\n    // add support for the paste event\n    paste: 'paste'\n  }\n});\n```\n\nTo prevent Ember from setting up a listener for a default event,\nspecify the event name with a `null` value in the `customEvents`\nproperty:\n\n```app/app.js\nimport Application from '@ember/application';\n\nlet App = Application.extend({\n  customEvents: {\n    // prevent listeners for mouseenter/mouseleave events\n    mouseenter: null,\n    mouseleave: null\n  }\n});\n```\n\nBy default, the application sets up these event listeners on the document\nbody. However, in cases where you are embedding an Ember application inside\nan existing page, you may want it to set up the listeners on an element\ninside the body.\n\nFor example, if only events inside a DOM element with the ID of `ember-app`\nshould be delegated, set your application's `rootElement` property:\n\n```app/app.js\nimport Application from '@ember/application';\n\nlet App = Application.extend({\n  rootElement: '#ember-app'\n});\n```\n\nThe `rootElement` can be either a DOM element or a jQuery-compatible selector\nstring. Note that *views appended to the DOM outside the root element will\nnot receive events.* If you specify a custom root element, make sure you only\nappend views inside it!\n\nTo learn more about the events Ember components use, see\n\n[components/handling-events](https://guides.emberjs.com/release/components/handling-events/#toc_event-names).\n\n### Initializers\n\nTo add behavior to the Application's boot process, you can define initializers in\nthe `app/initializers` directory, or with `ember generate initializer` using Ember CLI.\nThese files should export a named `initialize` function which will receive the created `application`\nobject as its first argument.\n\n```javascript\nexport function initialize(application) {\n  // application.inject('route', 'foo', 'service:foo');\n}\n```\n\nApplication initializers can be used for a variety of reasons including:\n\n- setting up external libraries\n- injecting dependencies\n- setting up event listeners in embedded apps\n- deferring the boot process using the `deferReadiness` and `advanceReadiness` APIs.\n\n### Routing\n\nIn addition to creating your application's router, `Application` is\nalso responsible for telling the router when to start routing. Transitions\nbetween routes can be logged with the `LOG_TRANSITIONS` flag, and more\ndetailed intra-transition logging can be logged with\nthe `LOG_TRANSITIONS_INTERNAL` flag:\n\n```javascript\nimport Application from '@ember/application';\n\nlet App = Application.create({\n  LOG_TRANSITIONS: true, // basic logging of successful transitions\n  LOG_TRANSITIONS_INTERNAL: true // detailed logging of all routing steps\n});\n```\n\nBy default, the router will begin trying to translate the current URL into\napplication state once the browser emits the `DOMContentReady` event. If you\nneed to defer routing, you can call the application's `deferReadiness()`\nmethod. Once routing can begin, call the `advanceReadiness()` method.\n\nIf there is any setup required before routing begins, you can implement a\n`ready()` method on your app that will be invoked immediately before routing\nbegins.",
+      "description": "An instance of `Application` is the starting point for every Ember\napplication. It instantiates, initializes and coordinates the\nobjects that make up your app.\n\nEach Ember app has one and only one `Application` object. Although\nEmber CLI creates this object implicitly, the `Application` class\nis defined in the `app/app.js`. You can define a `ready` method on the\n`Application` class, which will be run by Ember when the application is\ninitialized.\n\n```app/app.js\nconst App = Application.extend({\n  ready() {\n    // your code here\n  }\n})\n```\n\nBecause `Application` ultimately inherits from `Ember.Namespace`, any classes\nyou create will have useful string representations when calling `toString()`.\nSee the `Ember.Namespace` documentation for more information.\n\nWhile you can think of your `Application` as a container that holds the\nother classes in your application, there are several other responsibilities\ngoing on under-the-hood that you may want to understand. It is also important\nto understand that an `Application` is different from an `ApplicationInstance`.\nRefer to the Guides to understand the difference between these.\n\n### Event Delegation\n\nEmber uses a technique called _event delegation_. This allows the framework\nto set up a global, shared event listener instead of requiring each view to\ndo it manually. For example, instead of each view registering its own\n`mousedown` listener on its associated element, Ember sets up a `mousedown`\nlistener on the `body`.\n\nIf a `mousedown` event occurs, Ember will look at the target of the event and\nstart walking up the DOM node tree, finding corresponding views and invoking\ntheir `mouseDown` method as it goes.\n\n`Application` has a number of default events that it listens for, as\nwell as a mapping from lowercase events to camel-cased view method names. For\nexample, the `keypress` event causes the `keyPress` method on the view to be\ncalled, the `dblclick` event causes `doubleClick` to be called, and so on.\n\nIf there is a bubbling browser event that Ember does not listen for by\ndefault, you can specify custom events and their corresponding view method\nnames by setting the application's `customEvents` property:\n\n```app/app.js\nimport Application from '@ember/application';\n\nlet App = Application.extend({\n  customEvents: {\n    // add support for the paste event\n    paste: 'paste'\n  }\n});\n```\n\nTo prevent Ember from setting up a listener for a default event,\nspecify the event name with a `null` value in the `customEvents`\nproperty:\n\n```app/app.js\nimport Application from '@ember/application';\n\nlet App = Application.extend({\n  customEvents: {\n    // prevent listeners for mouseenter/mouseleave events\n    mouseenter: null,\n    mouseleave: null\n  }\n});\n```\n\nBy default, the application sets up these event listeners on the document\nbody. However, in cases where you are embedding an Ember application inside\nan existing page, you may want it to set up the listeners on an element\ninside the body.\n\nFor example, if only events inside a DOM element with the ID of `ember-app`\nshould be delegated, set your application's `rootElement` property:\n\n```app/app.js\nimport Application from '@ember/application';\n\nlet App = Application.extend({\n  rootElement: '#ember-app'\n});\n```\n\nThe `rootElement` can be either a DOM element or a CSS selector\nstring. Note that *views appended to the DOM outside the root element will\nnot receive events.* If you specify a custom root element, make sure you only\nappend views inside it!\n\nTo learn more about the events Ember components use, see\n\n[components/handling-events](https://guides.emberjs.com/release/components/handling-events/#toc_event-names).\n\n### Initializers\n\nTo add behavior to the Application's boot process, you can define initializers in\nthe `app/initializers` directory, or with `ember generate initializer` using Ember CLI.\nThese files should export a named `initialize` function which will receive the created `application`\nobject as its first argument.\n\n```javascript\nexport function initialize(application) {\n  // application.inject('route', 'foo', 'service:foo');\n}\n```\n\nApplication initializers can be used for a variety of reasons including:\n\n- setting up external libraries\n- injecting dependencies\n- setting up event listeners in embedded apps\n- deferring the boot process using the `deferReadiness` and `advanceReadiness` APIs.\n\n### Routing\n\nIn addition to creating your application's router, `Application` is\nalso responsible for telling the router when to start routing. Transitions\nbetween routes can be logged with the `LOG_TRANSITIONS` flag, and more\ndetailed intra-transition logging can be logged with\nthe `LOG_TRANSITIONS_INTERNAL` flag:\n\n```javascript\nimport Application from '@ember/application';\n\nlet App = Application.create({\n  LOG_TRANSITIONS: true, // basic logging of successful transitions\n  LOG_TRANSITIONS_INTERNAL: true // detailed logging of all routing steps\n});\n```\n\nBy default, the router will begin trying to translate the current URL into\napplication state once the browser emits the `DOMContentReady` event. If you\nneed to defer routing, you can call the application's `deferReadiness()`\nmethod. Once routing can begin, call the `advanceReadiness()` method.\n\nIf there is any setup required before routing begins, you can implement a\n`ready()` method on your app that will be invoked immediately before routing\nbegins.",
       "extends": "Engine",
       "uses": [
         "RegistryProxyMixin"
@@ -3637,7 +3507,7 @@
       "module": "@ember/canary-features",
       "namespace": "",
       "file": "packages/@ember/canary-features/index.ts",
-      "line": 26,
+      "line": 25,
       "description": "The hash of enabled Canary features. Add to this, any canary features\nbefore creating your application.",
       "static": 1,
       "since": "1.1.0",
@@ -5193,19 +5063,6 @@
       "class": "EmberENV",
       "module": "rsvp"
     },
-    {
-      "file": "packages/@ember/-internals/environment/lib/env.ts",
-      "line": 158,
-      "description": "Allows disabling the implicit this property fallback deprecation. This could be useful\nas a way to control the volume of deprecations that are issued by temporarily disabling\nthe implicit this fallback deprecations, which would allow the other deprecations to be more easily\nidentified in the console).\n\nNOTE: The fallback behavior **will be removed** in Ember 4.0.0, disabling **_IS NOT_**\na viable strategy for handling this deprecation.",
-      "itemtype": "property",
-      "name": "_DISABLE_PROPERTY_FALLBACK_DEPRECATION",
-      "type": "boolean",
-      "default": "false",
-      "access": "private",
-      "tagname": "",
-      "class": "EmberENV",
-      "module": "rsvp"
-    },
     {
       "file": "packages/@ember/-internals/extension-support/lib/container_debug_adapter.js",
       "line": 50,
@@ -5662,446 +5519,47 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 20,
-      "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 a `tagName`\n\nBy default `<LinkTo>` renders an `<a>` element. This can be overridden for a single use of\n`<LinkTo>` by supplying a `tagName` argument:\n\n```handlebars\n<LinkTo @route='photoGallery' @tagName='li'>\n  Great Hamster Photos\n</LinkTo>\n```\n\nThis produces:\n\n```html\n<li>\n  Great Hamster Photos\n</li>\n```\n\nIn general, this is not recommended.\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```",
+      "file": "packages/@ember/-internals/glimmer/lib/components/abstract-input.ts",
+      "line": 125,
+      "description": "The `change` and `input` actions need to be overridden in the `Input`\nsubclass. Unfortunately, some ember-source builds currently uses babel\nloose mode to transpile its classes. Having the `@action` decorator on the\nsuper class creates a getter on the prototype, and when the subclass\noverrides the method, the loose mode transpilation would emit something\nlike `Subclass.prototype['change'] = function change() { ... }`, which\nfails because `prototype['change']` is getter-only/readonly. The correct\nsolution is to use `Object.defineProperty(prototype, 'change', ...)` but\nthat requires disabling loose mode. For now, the workaround is to add the\ndecorator only on the subclass. This is more of a configuration issue on\nour own builds and doesn't really affect apps.",
+      "class": "Ember.Templates.helpers",
+      "module": "@ember/debug"
+    },
+    {
+      "file": "packages/@ember/-internals/glimmer/lib/components/input.ts",
+      "line": 45,
+      "description": "See [Ember.Templates.components.Input](/ember/release/classes/Ember.Templates.components/methods/Input?anchor=Input).",
       "itemtype": "method",
-      "name": "LinkTo",
-      "see": [
-        "{LinkComponent}"
-      ],
-      "access": "public",
-      "tagname": "",
-      "class": "Ember.Templates.components",
-      "module": "ember"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 254,
-      "description": "See [Ember.Templates.components.LinkTo](/ember/release/classes/Ember.Templates.components/methods/input?anchor=LinkTo).",
-      "itemtype": "method",
-      "name": "link-to",
-      "see": [
-        "{Ember.Templates.components.LinkTo}"
+      "name": "input",
+      "params": [
+        {
+          "name": "options",
+          "description": "",
+          "type": "Hash"
+        }
       ],
       "access": "public",
       "tagname": "",
       "class": "Ember.Templates.helpers",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 285,
-      "itemtype": "property",
-      "name": "route",
-      "access": "public",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 291,
-      "itemtype": "property",
-      "name": "model",
-      "access": "public",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 297,
-      "itemtype": "property",
-      "name": "models",
-      "access": "public",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 303,
-      "itemtype": "property",
-      "name": "query",
-      "access": "public",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 309,
-      "description": "Used to determine when this `LinkComponent` is active.",
-      "itemtype": "property",
-      "name": "current-when",
-      "access": "public",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 317,
-      "description": "Sets the `title` attribute of the `LinkComponent`'s HTML element.",
-      "itemtype": "property",
-      "name": "title",
-      "default": "null",
-      "access": "public",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 326,
-      "description": "Sets the `rel` attribute of the `LinkComponent`'s HTML element.",
-      "itemtype": "property",
-      "name": "rel",
-      "default": "null",
-      "access": "public",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 335,
-      "description": "Sets the `tabindex` attribute of the `LinkComponent`'s HTML element.",
-      "itemtype": "property",
-      "name": "tabindex",
-      "default": "null",
-      "access": "public",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 344,
-      "description": "Sets the `target` attribute of the `LinkComponent`'s HTML element.",
-      "since": "1.8.0",
-      "itemtype": "property",
-      "name": "target",
-      "default": "null",
-      "access": "public",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 354,
-      "description": "The CSS class to apply to `LinkComponent`'s element when its `active`\nproperty is `true`.",
-      "itemtype": "property",
-      "name": "activeClass",
-      "type": "String",
-      "default": "active",
-      "access": "public",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 365,
-      "description": "The CSS class to apply to `LinkComponent`'s element when its `loading`\nproperty is `true`.",
-      "itemtype": "property",
-      "name": "loadingClass",
-      "type": "String",
-      "default": "loading",
-      "access": "public",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 376,
-      "description": "The CSS class to apply to a `LinkComponent`'s element when its `disabled`\nproperty is `true`.",
-      "itemtype": "property",
-      "name": "disabledClass",
-      "type": "String",
-      "default": "disabled",
-      "access": "public",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 387,
-      "description": "Determines whether the `LinkComponent` will trigger routing via\nthe `replaceWith` routing strategy.",
-      "itemtype": "property",
-      "name": "replace",
-      "type": "Boolean",
-      "default": "false",
-      "access": "public",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 398,
-      "description": "Determines whether the `LinkComponent` will prevent the default\nbrowser action by calling preventDefault() to avoid reloading\nthe browser page.\n\nIf you need to trigger a full browser reload pass `@preventDefault={{false}}`:\n\n```handlebars\n<LinkTo @route='photoGallery' @model={{this.aPhotoId}} @preventDefault={{false}}>\n  {{this.aPhotoId.title}}\n</LinkTo>\n```",
-      "itemtype": "property",
-      "name": "preventDefault",
-      "type": "Boolean",
-      "default": "true",
-      "access": "private",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 418,
-      "description": "By default this component will forward `href`, `title`, `rel`, `tabindex`, and `target`\narguments to attributes on the component's element. When invoked with `{{link-to}}`, you can\nonly customize these attributes. When invoked with `<LinkTo>`, you can just use HTML\nattributes directly.",
-      "itemtype": "property",
-      "name": "attributeBindings",
-      "type": "Array | String",
-      "default": "['title', 'rel', 'tabindex', 'target']",
-      "access": "public",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 431,
-      "description": "By default this component will set classes on its element when any of the following arguments\nare truthy:\n\n* active\n* loading\n* disabled\n\nWhen these arguments are truthy, a class with the same name will be set on the element. When\nfalsy, the associated class will not be on the element.",
-      "itemtype": "property",
-      "name": "classNameBindings",
-      "type": "Array",
-      "default": "['active', 'loading', 'disabled', 'ember-transitioning-in', 'ember-transitioning-out']",
-      "access": "public",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 449,
-      "description": "By default this component responds to the `click` event. When the component element is an\n`<a>` element, activating the link in another way, such as using the keyboard, triggers the\nclick event.",
-      "itemtype": "property",
-      "name": "eventName",
-      "type": "String",
-      "default": "click",
-      "access": "private",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 464,
-      "description": "Triggers the `LinkComponent`'s routing behavior. If\n`eventName` is changed to a value other than `click`\nthe routing behavior will trigger on that custom event\ninstead.",
-      "itemtype": "event",
-      "name": "click",
-      "access": "private",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 474,
-      "description": "An overridable method called when `LinkComponent` objects are instantiated.\n\nExample:\n\n```app/components/my-link.js\nimport LinkComponent from '@ember/routing/link-component';\n\nexport default LinkComponent.extend({\n  init() {\n    this._super(...arguments);\n    console.log('Event is ' + this.get('eventName'));\n  }\n});\n```\n\nNOTE: If you do override `init` for a framework class like `Component`,\nbe sure to call `this._super(...arguments)` in your\n`init` declaration! If 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",
-      "access": "private",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 556,
-      "description": "Accessed as a classname binding to apply the component's `disabledClass`\nCSS `class` to the element when the link is disabled.\n\nWhen `true`, interactions with the element will not trigger route changes.",
-      "itemtype": "property",
-      "name": "disabled",
-      "access": "private",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 579,
-      "description": "Accessed as a classname binding to apply the component's `activeClass`\nCSS `class` to the element when the link is active.\n\nThis component is considered active when its `currentWhen` property is `true`\nor the application's current route is the route this component would trigger\ntransitions into.\n\nThe `currentWhen` property can match against multiple routes by separating\nroute names using the ` ` (space) character.",
-      "itemtype": "property",
-      "name": "active",
-      "access": "private",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 634,
-      "description": "Method to assert that LinkTo is not used inside of a routeless engine. This method is\noverridden in ember-engines link-to-external component to just be a noop, since the\nlink-to-external component extends the link-to component.",
-      "itemtype": "method",
-      "name": "assertLinkToOrigin",
-      "access": "private",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 711,
-      "description": "Event handler that invokes the link, activating the associated route.",
-      "itemtype": "method",
-      "name": "_invoke",
-      "params": [
-        {
-          "name": "event",
-          "description": "",
-          "type": "Event"
-        }
-      ],
-      "access": "private",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 790,
-      "description": "Sets the element's `href` attribute to the url for\nthe `LinkComponent`'s targeted route.\n\nIf the `LinkComponent`'s `tagName` is changed to a value other\nthan `a`, this property will be ignored.",
-      "itemtype": "property",
-      "name": "href",
-      "access": "private",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/-link-to.ts",
-      "line": 870,
-      "description": "The default href value to use while a link-to is loading.\nOnly applies when tagName is 'a'",
-      "itemtype": "property",
-      "name": "loadingHref",
-      "type": "String",
-      "default": "#",
-      "access": "private",
-      "tagname": "",
-      "class": "LinkComponent",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/abstract-input.ts",
-      "line": 149,
-      "description": "The `change` and `input` actions need to be overridden in the `Input`\nsubclass. Unfortunately, some ember-source builds currently uses babel\nloose mode to transpile its classes. Having the `@action` decorator on the\nsuper class creates a getter on the prototype, and when the subclass\noverrides the method, the loose mode transpilation would emit something\nlike `Subclass.prototype['change'] = function change() { ... }`, which\nfails because `prototype['change']` is getter-only/readonly. The correct\nsolution is to use `Object.defineProperty(prototype, 'change', ...)` but\nthat requires disabling loose mode. For now, the workaround is to add the\ndecorator only on the subclass. This is more of a configuration issue on\nour own builds and doesn't really affect apps.",
-      "class": "Checkbox",
-      "module": "@ember/component"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/checkbox.ts",
-      "line": 39,
-      "description": "By default, this component will add the `ember-checkbox` class to the component's element.",
-      "itemtype": "property",
-      "name": "classNames",
-      "type": "Array | String",
-      "default": "['ember-checkbox']",
-      "access": "public",
-      "tagname": "",
-      "class": "Checkbox",
-      "module": "@ember/component"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/checkbox.ts",
-      "line": 51,
-      "description": "By default this component will forward a number of arguments to attributes on the the\ncomponent's element:\n\n* indeterminate\n* disabled\n* tabindex\n* name\n* autofocus\n* required\n* form\n\nWhen invoked with curly braces, this is the exhaustive list of HTML attributes you can\ncustomize (i.e. `{{input type=\"checkbox\" disabled=true}}`).\n\nWhen invoked with angle bracket invocation, this list is irrelevant, because you can use HTML\nattribute syntax to customize the element (i.e.\n`<Input @type=\"checkbox\" disabled data-custom=\"custom value\" />`). However, `@type` and\n`@checked` must be passed as named arguments, not attributes.",
-      "itemtype": "property",
-      "name": "attributeBindings",
-      "type": "Array | String",
-      "default": "['type', 'checked', 'indeterminate', 'disabled', 'tabindex', 'name', 'autofocus', 'required', 'form']",
-      "access": "public",
-      "tagname": "",
-      "class": "Checkbox",
-      "module": "@ember/component"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/checkbox.ts",
-      "line": 88,
-      "description": "Sets the `type` attribute of the `Checkbox`'s element",
-      "itemtype": "property",
-      "name": "disabled",
-      "default": "false",
-      "access": "private",
-      "tagname": "",
-      "class": "Checkbox",
-      "module": "@ember/component"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/checkbox.ts",
-      "line": 97,
-      "description": "Sets the `disabled` attribute of the `Checkbox`'s element",
-      "itemtype": "property",
-      "name": "disabled",
-      "default": "false",
-      "access": "public",
-      "tagname": "",
-      "class": "Checkbox",
-      "module": "@ember/component"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/checkbox.ts",
-      "line": 106,
-      "description": "Corresponds to the `indeterminate` property of the `Checkbox`'s element",
-      "itemtype": "property",
-      "name": "disabled",
-      "default": "false",
-      "access": "public",
-      "tagname": "",
-      "class": "Checkbox",
-      "module": "@ember/component"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/checkbox.ts",
-      "line": 115,
-      "description": "Whenever the checkbox is inserted into the DOM, perform initialization steps, which include\nsetting the indeterminate property if needed.\n\nIf this method is overridden, `super` must be called.",
-      "itemtype": "method",
-      "name": "",
-      "access": "public",
-      "tagname": "",
-      "class": "Checkbox",
-      "module": "@ember/component"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/checkbox.ts",
-      "line": 129,
-      "description": "Whenever the `change` event is fired on the checkbox, update its `checked` property to reflect\nwhether the checkbox is checked.\n\nIf this method is overridden, `super` must be called.",
-      "itemtype": "method",
-      "name": "",
-      "access": "public",
-      "tagname": "",
-      "class": "Checkbox",
       "module": "@ember/component"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/components/input.ts",
-      "line": 48,
-      "description": "See [Ember.Templates.components.Input](/ember/release/classes/Ember.Templates.components/methods/Input?anchor=Input).",
+      "line": 54,
+      "description": "An opaque interface which can be imported and used in strict-mode\ntemplates to call <Input>.\n\nSee [Ember.Templates.components.Input](/ember/release/classes/Ember.Templates.components/methods/Input?anchor=Input).",
       "itemtype": "method",
-      "name": "input",
-      "params": [
-        {
-          "name": "options",
-          "description": "",
-          "type": "Hash"
-        }
+      "name": "Input",
+      "see": [
+        "{Ember.Templates.components.Input}"
       ],
       "access": "public",
       "tagname": "",
-      "class": "Ember.Templates.helpers",
+      "class": "@ember/component",
       "module": "@ember/component"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/components/input.ts",
-      "line": 57,
+      "line": 66,
       "description": "The `Input` component lets you create an HTML `<input>` element.\n\n```handlebars\n<Input @value=\"987\" />\n```\n\ncreates an `<input>` element with `type=\"text\"` and value set to 987.\n\n### Text field\n\nIf no `type` argument is specified, a default of type 'text' is used.\n\n```handlebars\nSearch:\n<Input @value={{this.searchWord}} />\n```\n\nIn this example, the initial value in the `<input>` will be set to the value of\n`this.searchWord`. If the user changes the text, the value of `this.searchWord` will also be\nupdated.\n\n### Actions\n\nThe `Input` component takes a number of arguments with callbacks that are invoked in response to\nuser events.\n\n* `enter`\n* `insert-newline`\n* `escape-press`\n* `focus-in`\n* `focus-out`\n* `key-down`\n* `key-press`\n* `key-up`\n\nThese callbacks are passed to `Input` like this:\n\n```handlebars\n<Input @value={{this.searchWord}} @enter={{this.query}} />\n```\n\nStarting with Ember Octane, we recommend using the `{{on}}` modifier to call actions\non specific events, such as the input event.\n\n```handlebars\n<label for=\"input-name\">Name:</label>\n<Input\n  @id=\"input-name\"\n  @value={{this.name}}\n  {{on \"input\" this.validateName}}\n/>\n```\n\nThe event name (e.g. `focusout`, `input`, `keydown`) always follows the casing\nthat the HTML standard uses.\n\n### `<input>` HTML Attributes to Avoid\n\nIn most cases, if you want to pass an attribute to the underlying HTML `<input>` element, you\ncan pass the attribute directly, just like any other Ember component.\n\n```handlebars\n<Input @type=\"text\" size=\"10\" />\n```\n\nIn this example, the `size` attribute will be applied to the underlying `<input>` element in the\noutputted HTML.\n\nHowever, there are a few attributes where you **must** use the `@` version.\n\n* `@type`: This argument is used to control which Ember component is used under the hood\n* `@value`: The `@value` argument installs a two-way binding onto the element. If you wanted a\n  one-way binding, use `<input>` with the `value` property and the `input` event instead.\n* `@checked` (for checkboxes): like `@value`, the `@checked` argument installs a two-way binding\n  onto the element. If you wanted a one-way binding, use `<input type=\"checkbox\">` with\n  `checked` and the `input` event instead.\n\n### Extending `TextField`\n\nInternally, `<Input @type=\"text\" />` creates an instance of `TextField`, passing arguments from\nthe helper to `TextField`'s `create` method. Subclassing `TextField` is supported but not\nrecommended.\n\nSee [TextField](/ember/release/classes/TextField)\n\n### Checkbox\n\nTo create an `<input type=\"checkbox\">`:\n\n```handlebars\nEmberize Everything:\n<Input @type=\"checkbox\" @checked={{this.isEmberized}} name=\"isEmberized\" />\n```\n\nThis will bind the checked state of this checkbox to the value of `isEmberized` -- if either one\nchanges, it will be reflected in the other.\n\n### Extending `Checkbox`\n\nInternally, `<Input @type=\"checkbox\" />` creates an instance of `Checkbox`. Subclassing\n`TextField` is supported but not recommended.\n\nSee [Checkbox](/ember/release/classes/Checkbox)",
       "itemtype": "method",
       "name": "Input",
@@ -6123,164 +5581,108 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/components/input.ts",
-      "line": 174,
+      "line": 183,
       "description": "The HTML class attribute.",
       "class": "Ember.Templates.components",
       "module": "@ember/component"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/components/input.ts",
-      "line": 185,
+      "line": 194,
       "description": "The HTML type attribute.",
       "class": "Ember.Templates.components",
       "module": "@ember/component"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/components/internal.ts",
-      "line": 45,
+      "line": 37,
       "description": "The default HTML id attribute. We don't really _need_ one, this is just\nadded for compatibility as it's hard to tell if people rely on it being\npresent, and it doens't really hurt.\n\nHowever, don't rely on this internally, like passing it to `getElementId`.\nThis can be (and often is) overriden by passing an `id` attribute on the\ninvocation, which shadows this default id via `...attributes`.",
-      "class": "TextField",
+      "class": "Ember.Templates.components",
       "module": "@ember/component"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/components/internal.ts",
-      "line": 58,
+      "line": 50,
       "description": "The default HTML class attribute. Similar to the above, we don't _need_\nthem, they are just added for compatibility as it's similarly hard to tell\nif people rely on it in their CSS etc, and it doens't really hurt.",
-      "class": "TextField",
-      "module": "@ember/component"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/text-field.ts",
-      "line": 54,
-      "description": "By default, this component will add the `ember-text-field` class to the component's element.",
-      "itemtype": "property",
-      "name": "classNames",
-      "type": "Array | String",
-      "default": "['ember-text-field']",
-      "access": "public",
-      "tagname": "",
-      "class": "TextField",
-      "module": "@ember/component"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/text-field.ts",
-      "line": 65,
-      "description": "By default this component will forward a number of arguments to attributes on the the\ncomponent's element:\n\n* accept\n* autocomplete\n* autosave\n* dir\n* formaction\n* formenctype\n* formmethod\n* formnovalidate\n* formtarget\n* height\n* inputmode\n* lang\n* list\n* type\n* max\n* min\n* multiple\n* name\n* pattern\n* size\n* step\n* value\n* width\n\nWhen invoked with `{{input type=\"text\"}}`, you can only customize these attributes. When invoked\nwith `<Input @type=\"text\" />`, you can just use HTML attributes directly.",
-      "itemtype": "property",
-      "name": "attributeBindings",
-      "type": "Array | String",
-      "default": "['accept', 'autocomplete', 'autosave', 'dir', 'formaction', 'formenctype', 'formmethod', 'formnovalidate', 'formtarget', 'height', 'inputmode', 'lang', 'list', 'type', 'max', 'min', 'multiple', 'name', 'pattern', 'size', 'step', 'value', 'width']",
-      "access": "public",
-      "tagname": "",
-      "class": "TextField",
-      "module": "@ember/component"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/text-field.ts",
-      "line": 127,
-      "description": "As the user inputs text, this property is updated to reflect the `value` property of the HTML\nelement.",
-      "itemtype": "property",
-      "name": "value",
-      "type": "String",
-      "default": "\"\"",
-      "access": "public",
-      "tagname": "",
-      "class": "TextField",
-      "module": "@ember/component"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/text-field.ts",
-      "line": 138,
-      "description": "The `type` attribute of the input element.",
-      "itemtype": "property",
-      "name": "type",
-      "type": "String",
-      "default": "\"text\"",
-      "access": "public",
-      "tagname": "",
-      "class": "TextField",
+      "class": "Ember.Templates.components",
       "module": "@ember/component"
     },
     {
-      "file": "packages/@ember/-internals/glimmer/lib/components/text-field.ts",
-      "line": 162,
-      "description": "The `size` of the text field in characters.",
-      "itemtype": "property",
-      "name": "size",
-      "type": "String",
-      "default": "null",
+      "file": "packages/@ember/-internals/glimmer/lib/components/link-to.ts",
+      "line": 40,
+      "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",
       "access": "public",
       "tagname": "",
-      "class": "TextField",
+      "class": "Ember.Templates.components",
       "module": "@ember/component"
     },
     {
-      "file": "packages/@ember/-internals/glimmer/lib/components/text-field.ts",
-      "line": 172,
-      "description": "The `pattern` attribute of input element.",
-      "itemtype": "property",
-      "name": "pattern",
-      "type": "String",
-      "default": "null",
+      "file": "packages/@ember/-internals/glimmer/lib/components/link-to.ts",
+      "line": 252,
+      "description": "See [Ember.Templates.components.LinkTo](/ember/release/classes/Ember.Templates.components/methods/input?anchor=LinkTo).",
+      "itemtype": "method",
+      "name": "link-to",
+      "see": [
+        "{Ember.Templates.components.LinkTo}"
+      ],
       "access": "public",
       "tagname": "",
-      "class": "TextField",
-      "module": "@ember/component"
+      "class": "Ember.Templates.helpers",
+      "module": "@ember/routing"
     },
     {
-      "file": "packages/@ember/-internals/glimmer/lib/components/text-field.ts",
-      "line": 182,
-      "description": "The `min` attribute of input element used with `type=\"number\"` or `type=\"range\"`.",
-      "itemtype": "property",
-      "name": "min",
-      "type": "String",
-      "default": "null",
-      "since": "1.4.0",
+      "file": "packages/@ember/-internals/glimmer/lib/components/link-to.ts",
+      "line": 261,
+      "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",
+      "see": [
+        "{Ember.Templates.components.LinkTo}"
+      ],
       "access": "public",
       "tagname": "",
-      "class": "TextField",
-      "module": "@ember/component"
+      "class": "@ember/routing",
+      "module": "@ember/routing"
     },
     {
-      "file": "packages/@ember/-internals/glimmer/lib/components/text-field.ts",
-      "line": 193,
-      "description": "The `max` attribute of input element used with `type=\"number\"` or `type=\"range\"`.",
-      "itemtype": "property",
-      "name": "max",
-      "type": "String",
-      "default": "null",
-      "since": "1.4.0",
+      "file": "packages/@ember/-internals/glimmer/lib/components/textarea.ts",
+      "line": 9,
+      "description": "The `Textarea` component inserts a new instance of `<textarea>` tag into the template.\n\nThe `@value` argument provides the content of the `<textarea>`.\n\nThis template:\n\n```handlebars\n<Textarea @value=\"A bunch of text\" />\n```\n\nWould result in the following HTML:\n\n```html\n<textarea class=\"ember-text-area\">\n  A bunch of text\n</textarea>\n```\n\nThe `@value` argument is two-way bound. If the user types text into the textarea, the `@value`\nargument is updated. If the `@value` argument is updated, the text in the textarea is updated.\n\nIn the following example, the `writtenWords` property on the component will be updated as the user\ntypes 'Lots of text' into the text area of their browser's window.\n\n```app/components/word-editor.js\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\n\nexport default class WordEditorComponent extends Component {\n  @tracked writtenWords = \"Lots of text that IS bound\";\n}\n```\n\n```handlebars\n<Textarea @value={{writtenWords}} />\n```\n\nWould result in the following HTML:\n\n```html\n<textarea class=\"ember-text-area\">\n  Lots of text that IS bound\n</textarea>\n```\n\nIf you wanted a one way binding, you could use the `<textarea>` element directly, and use the\n`value` DOM property and the `input` event.\n\n### Actions\n\nThe `Textarea` component takes a number of arguments with callbacks that are invoked in\nresponse to user events.\n\n* `enter`\n* `insert-newline`\n* `escape-press`\n* `focus-in`\n* `focus-out`\n* `key-press`\n\nThese callbacks are passed to `Textarea` like this:\n\n```handlebars\n<Textarea @value={{this.searchWord}} @enter={{this.query}} />\n```\n\n## Classic Invocation Syntax\n\nThe `Textarea` component can also be invoked using curly braces, just like any other Ember\ncomponent.\n\nFor example, this is an invocation using angle-bracket notation:\n\n```handlebars\n<Textarea @value={{this.searchWord}} @enter={{this.query}} />\n```\n\nYou could accomplish the same thing using classic invocation:\n\n```handlebars\n{{textarea value=this.searchWord enter=this.query}}\n```\n\nThe main difference is that angle-bracket invocation supports any HTML attribute using HTML\nattribute syntax, because attributes and arguments have different syntax when using angle-bracket\ninvocation. Curly brace invocation, on the other hand, only has a single syntax for arguments,\nand components must manually map attributes onto component arguments.\n\nWhen using classic invocation with `{{textarea}}`, only the following attributes are mapped onto\narguments:\n\n* rows\n* cols\n* name\n* selectionEnd\n* selectionStart\n* autocomplete\n* wrap\n* lang\n* dir\n* value\n\n## Classic `layout` and `layoutName` properties\n\nBecause HTML `textarea` elements do not contain inner HTML the `layout` and\n`layoutName` properties will not be applied.",
+      "itemtype": "method",
+      "name": "Textarea",
       "access": "public",
       "tagname": "",
-      "class": "TextField",
+      "class": "Ember.Templates.components",
       "module": "@ember/component"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/components/textarea.ts",
-      "line": 11,
-      "description": "The `Textarea` component inserts a new instance of `<textarea>` tag into the template.\n\nThe `@value` argument provides the content of the `<textarea>`.\n\nThis template:\n\n```handlebars\n<Textarea @value=\"A bunch of text\" />\n```\n\nWould result in the following HTML:\n\n```html\n<textarea class=\"ember-text-area\">\n  A bunch of text\n</textarea>\n```\n\nThe `@value` argument is two-way bound. If the user types text into the textarea, the `@value`\nargument is updated. If the `@value` argument is updated, the text in the textarea is updated.\n\nIn the following example, the `writtenWords` property on the component will be updated as the user\ntypes 'Lots of text' into the text area of their browser's window.\n\n```app/components/word-editor.js\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\n\nexport default class WordEditorComponent extends Component {\n  @tracked writtenWords = \"Lots of text that IS bound\";\n}\n```\n\n```handlebars\n<Textarea @value={{writtenWords}} />\n```\n\nWould result in the following HTML:\n\n```html\n<textarea class=\"ember-text-area\">\n  Lots of text that IS bound\n</textarea>\n```\n\nIf you wanted a one way binding, you could use the `<textarea>` element directly, and use the\n`value` DOM property and the `input` event.\n\n### Actions\n\nThe `Textarea` component takes a number of arguments with callbacks that are invoked in\nresponse to user events.\n\n* `enter`\n* `insert-newline`\n* `escape-press`\n* `focus-in`\n* `focus-out`\n* `key-press`\n\nThese callbacks are passed to `Textarea` like this:\n\n```handlebars\n<Textarea @value={{this.searchWord}} @enter={{this.query}} />\n```\n\n## Classic Invocation Syntax\n\nThe `Textarea` component can also be invoked using curly braces, just like any other Ember\ncomponent.\n\nFor example, this is an invocation using angle-bracket notation:\n\n```handlebars\n<Textarea @value={{this.searchWord}} @enter={{this.query}} />\n```\n\nYou could accomplish the same thing using classic invocation:\n\n```handlebars\n{{textarea value=this.searchWord enter=this.query}}\n```\n\nThe main difference is that angle-bracket invocation supports any HTML attribute using HTML\nattribute syntax, because attributes and arguments have different syntax when using angle-bracket\ninvocation. Curly brace invocation, on the other hand, only has a single syntax for arguments,\nand components must manually map attributes onto component arguments.\n\nWhen using classic invocation with `{{textarea}}`, only the following attributes are mapped onto\narguments:\n\n* rows\n* cols\n* name\n* selectionEnd\n* selectionStart\n* autocomplete\n* wrap\n* lang\n* dir\n* value\n\n## Classic `layout` and `layoutName` properties\n\nBecause HTML `textarea` elements do not contain inner HTML the `layout` and\n`layoutName` properties will not be applied.",
+      "line": 122,
+      "description": "See Ember.Templates.components.Textarea.",
       "itemtype": "method",
-      "name": "Textarea",
+      "name": "textarea",
       "see": [
-        "{TextArea}"
+        "{Ember.Templates.components.Textarea}"
       ],
       "access": "public",
       "tagname": "",
-      "class": "Ember.Templates.components",
+      "class": "Ember.Templates.helpers",
       "module": "@ember/component"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/components/textarea.ts",
-      "line": 125,
-      "description": "See Ember.Templates.components.Textarea.",
+      "line": 131,
+      "description": "An opaque interface which can be imported and used in strict-mode\ntemplates to call <Textarea>.\n\nSee [Ember.Templates.components.Textarea](/ember/release/classes/Ember.Templates.components/methods/Textarea?anchor=Input).",
       "itemtype": "method",
-      "name": "textarea",
+      "name": "Textarea",
       "see": [
-        "{Ember.Templates.components.textarea}"
+        "{Ember.Templates.components.Textarea}"
       ],
       "access": "public",
       "tagname": "",
-      "class": "Ember.Templates.helpers",
+      "class": "@ember/component",
       "module": "@ember/component"
     },
     {
@@ -6495,31 +5897,6 @@
       "class": "Ember.Templates.helpers",
       "module": "ember"
     },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/helpers/query-param.ts",
-      "line": 11,
-      "description": "This is a helper to be used in conjunction with the link-to helper.\nIt will supply url query parameters to the target route.",
-      "example": [
-        " In this example we are setting the `direction` query param to the value `\"asc\"`\n\n```app/templates/application.hbs\n<LinkTo\n  @route=\"posts\"\n  {{query-params direction=\"asc\"}}\n>\n  Sort\n</LinkTo>\n```"
-      ],
-      "itemtype": "method",
-      "name": "query-params",
-      "params": [
-        {
-          "name": "hash",
-          "description": "takes a hash of query parameters",
-          "type": "Object"
-        }
-      ],
-      "return": {
-        "description": "A `QueryParams` object for `{{link-to}}`",
-        "type": "Object"
-      },
-      "access": "public",
-      "tagname": "",
-      "class": "Ember.Templates.helpers",
-      "module": "ember"
-    },
     {
       "file": "packages/@ember/-internals/glimmer/lib/helpers/readonly.ts",
       "line": 8,
@@ -6736,7 +6113,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 753,
+      "line": 752,
       "description": "Normally, Ember's component model is \"write-only\". The component takes a\nbunch of attributes that it got passed in, and uses them to render its\ntemplate.\n\nOne nice thing about this model is that if you try to set a value to the\nsame thing as last time, Ember (through HTMLBars) will avoid doing any\nwork on the DOM.\n\nThis is not just a performance optimization. If an attribute has not\nchanged, it is important not to clobber the element's \"hidden state\".\nFor example, if you set an input's `value` to the same value as before,\nit will clobber selection state and cursor position. In other words,\nsetting an attribute is not **always** idempotent.\n\nThis method provides a way to read an element's attribute and also\nupdate the last value Ember knows about at the same time. This makes\nsetting an attribute idempotent.\n\nIn particular, what this means is that if you get an `<input>` element's\n`value` attribute and then re-render the template with the same value,\nit will avoid clobbering the cursor and selection position.\nSince most attribute sets are idempotent in the browser, you typically\ncan get away with reading attributes using jQuery, but the most reliable\nway to do so is through this method.",
       "itemtype": "method",
       "name": "readDOMAttr",
@@ -6757,7 +6134,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 804,
+      "line": 803,
       "description": "The WAI-ARIA role of the control represented by this view. For example, a\nbutton may have a role of type 'button', or a pane may have a role of\ntype 'alertdialog'. This property is used by assistive software to help\nvisually challenged users navigate rich web applications.\n\nThe full list of valid WAI-ARIA roles is available at:\n[https://www.w3.org/TR/wai-aria/#roles_categorization](https://www.w3.org/TR/wai-aria/#roles_categorization)",
       "itemtype": "property",
       "name": "ariaRole",
@@ -6770,7 +6147,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 819,
+      "line": 818,
       "description": "Enables components to take a list of parameters as arguments.\nFor example, a component that takes two parameters with the names\n`name` and `age`:\n\n```app/components/my-component.js\nimport Component from '@ember/component';\n\nlet MyComponent = Component.extend();\n\nMyComponent.reopenClass({\n  positionalParams: ['name', 'age']\n});\n\nexport default MyComponent;\n```\n\nIt can then be invoked like this:\n\n```hbs\n{{my-component \"John\" 38}}\n```\n\nThe parameters can be referred to just like named parameters:\n\n```hbs\nName: {{name}}, Age: {{age}}.\n```\n\nUsing a string instead of an array allows for an arbitrary number of\nparameters:\n\n```app/components/my-component.js\nimport Component from '@ember/component';\n\nlet MyComponent = Component.extend();\n\nMyComponent.reopenClass({\n  positionalParams: 'names'\n});\n\nexport default MyComponent;\n```\n\nIt can then be invoked like this:\n\n```hbs\n{{my-component \"John\" \"Michael\" \"Scott\"}}\n```\nThe parameters can then be referred to by enumerating over the list:\n\n```hbs\n{{#each names as |name|}}{{name}}{{/each}}\n```",
       "static": 1,
       "access": "public",
@@ -6783,7 +6160,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 880,
+      "line": 879,
       "description": "Called when the attributes passed into the component have been updated.\nCalled both during the initial render of a container and during a rerender.\nCan be used in place of an observer; code placed here will be executed\nevery time any attribute updates.",
       "itemtype": "method",
       "name": "didReceiveAttrs",
@@ -6795,7 +6172,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 891,
+      "line": 890,
       "description": "Called when the attributes passed into the component have been updated.\nCalled both during the initial render of a container and during a rerender.\nCan be used in place of an observer; code placed here will be executed\nevery time any attribute updates.",
       "itemtype": "event",
       "name": "didReceiveAttrs",
@@ -6807,7 +6184,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 901,
+      "line": 900,
       "description": "Called after a component has been rendered, both on initial render and\nin subsequent rerenders.",
       "itemtype": "method",
       "name": "didRender",
@@ -6819,7 +6196,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 910,
+      "line": 909,
       "description": "Called after a component has been rendered, both on initial render and\nin subsequent rerenders.",
       "itemtype": "event",
       "name": "didRender",
@@ -6831,7 +6208,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 918,
+      "line": 917,
       "description": "Called before a component has been rendered, both on initial render and\nin subsequent rerenders.",
       "itemtype": "method",
       "name": "willRender",
@@ -6843,7 +6220,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 927,
+      "line": 926,
       "description": "Called before a component has been rendered, both on initial render and\nin subsequent rerenders.",
       "itemtype": "event",
       "name": "willRender",
@@ -6855,7 +6232,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 935,
+      "line": 934,
       "description": "Called when the attributes passed into the component have been changed.\nCalled only during a rerender, not during an initial render.",
       "itemtype": "method",
       "name": "didUpdateAttrs",
@@ -6867,7 +6244,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 944,
+      "line": 943,
       "description": "Called when the attributes passed into the component have been changed.\nCalled only during a rerender, not during an initial render.",
       "itemtype": "event",
       "name": "didUpdateAttrs",
@@ -6879,7 +6256,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 952,
+      "line": 951,
       "description": "Called when the component is about to update and rerender itself.\nCalled only during a rerender, not during an initial render.",
       "itemtype": "method",
       "name": "willUpdate",
@@ -6891,7 +6268,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 961,
+      "line": 960,
       "description": "Called when the component is about to update and rerender itself.\nCalled only during a rerender, not during an initial render.",
       "itemtype": "event",
       "name": "willUpdate",
@@ -6903,7 +6280,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 969,
+      "line": 968,
       "description": "Called when the component has updated and rerendered itself.\nCalled only during a rerender, not during an initial render.",
       "itemtype": "method",
       "name": "didUpdate",
@@ -6915,7 +6292,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 978,
+      "line": 977,
       "description": "Called when the component has updated and rerendered itself.\nCalled only during a rerender, not during an initial render.",
       "itemtype": "event",
       "name": "didUpdate",
@@ -6927,7 +6304,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 986,
+      "line": 985,
       "description": "Layout can be used to wrap content in a component.",
       "itemtype": "property",
       "name": "layout",
@@ -6939,7 +6316,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 993,
+      "line": 992,
       "description": "The name of the layout to lookup if no layout is provided.\nBy default `Component` will lookup a template with this name in\n`Ember.TEMPLATES` (a shared global object).",
       "itemtype": "property",
       "name": "layoutName",
@@ -6952,30 +6329,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 1003,
-      "description": "Returns a jQuery object for this component's element. If you pass in a selector\nstring, this method will return a jQuery object, using the current element\nas its buffer.\n\nFor example, calling `component.$('li')` will return a jQuery object containing\nall of the `li` elements inside the DOM element of this component.\n\nPlease note that jQuery integration is off by default and this feature will\nnot work properly. To enable this feature, you can read the instructions in\nthe [jquery-integration optional feature guide](https://guides.emberjs.com/release/configuring-ember/optional-features/#toc_jquery-integration).",
-      "itemtype": "method",
-      "name": "$",
-      "params": [
-        {
-          "name": "selector",
-          "description": "a jQuery-compatible selector string",
-          "type": "String",
-          "optional": true
-        }
-      ],
-      "return": {
-        "description": "the jQuery object for the DOM node",
-        "type": "JQuery"
-      },
-      "access": "public",
-      "tagname": "",
-      "class": "Component",
-      "module": "@ember/component"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 1020,
+      "line": 1002,
       "description": "The HTML `id` of the component's element in the DOM. You can provide this\nvalue yourself but it must be unique (just as in HTML):\n\n```handlebars\n{{my-component elementId=\"a-really-cool-id\"}}\n```\n\n```handlebars\n<MyComponent @elementId=\"a-really-cool-id\" />\n```\nIf not manually set a default value will be provided by the framework.\nOnce rendered an element's `elementId` is considered immutable and you\nshould never change it. If you need to compute a dynamic value for the\n`elementId`, you should do this when the component or element is being\ninstantiated:\n\n```javascript\nexport default Component.extend({\n  init() {\n    this._super(...arguments);\n\n    var index = this.get('index');\n    this.set('elementId', `component-id${index}`);\n  }\n});\n```",
       "itemtype": "property",
       "name": "elementId",
@@ -6999,7 +6353,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
-      "line": 91,
+      "line": 85,
       "description": "On a class-based helper, it may be useful to force a recomputation of that\nhelpers value. This is akin to `rerender` on a component.\n\nFor example, this component will rerender when the `currentUser` on a\nsession service changes:\n\n```app/helpers/current-user-email.js\nimport Helper from '@ember/component/helper'\nimport { inject as service } from '@ember/service'\nimport { observer } from '@ember/object'\n\nexport default Helper.extend({\n  session: service(),\n\n  onNewUser: observer('session.currentUser', function() {\n    this.recompute();\n  }),\n\n  compute() {\n    return this.get('session.currentUser.email');\n  }\n});\n```",
       "itemtype": "method",
       "name": "recompute",
@@ -7011,7 +6365,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
-      "line": 124,
+      "line": 118,
       "description": "Override this function when writing a class-based helper.",
       "itemtype": "method",
       "name": "compute",
@@ -7035,7 +6389,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
-      "line": 256,
+      "line": 231,
       "description": "In many cases it is not necessary to use the full `Helper` class.\nThe `helper` method create pure-function helpers without instances.\nFor example:\n\n```app/helpers/format-currency.js\nimport { helper } from '@ember/component/helper';\n\nexport default helper(function([cents], {currency}) {\n  return `${currency}${cents * 0.01}`;\n});\n```",
       "static": 1,
       "params": [
@@ -7680,7 +7034,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 431,
+      "line": 430,
       "itemtype": "method",
       "name": "mixin",
       "params": [
@@ -7704,7 +7058,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 560,
+      "line": 559,
       "itemtype": "method",
       "name": "create",
       "static": 1,
@@ -7722,7 +7076,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 592,
+      "line": 591,
       "itemtype": "method",
       "name": "reopen",
       "params": [
@@ -7739,7 +7093,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 614,
+      "line": 613,
       "itemtype": "method",
       "name": "apply",
       "params": [
@@ -7758,7 +7112,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 633,
+      "line": 632,
       "itemtype": "method",
       "name": "detect",
       "params": [
@@ -7778,7 +7132,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/mixin.ts",
-      "line": 750,
+      "line": 749,
       "description": "Specify a method that observes property changes.\n\n```javascript\nimport EmberObject from '@ember/object';\nimport { observer } from '@ember/object';\n\nexport default EmberObject.extend({\n  valueObserver: observer('value', function() {\n    // Executes whenever the \"value\" property changes\n  })\n});\n```\n\nAlso available as `Function.prototype.observes` if prototype extensions are\nenabled.",
       "itemtype": "method",
       "name": "observer",
@@ -8002,7 +7356,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/property_get.ts",
-      "line": 47,
+      "line": 41,
       "description": "Gets the value of a property on an object. If the property is computed,\nthe function will be invoked. If the property is not defined but the\nobject implements the `unknownProperty` method then that will be invoked.\n\n```javascript\nimport { get } from '@ember/object';\nget(obj, \"name\");\n```\n\nIf you plan to run on IE8 and older browsers then you should use this\nmethod anytime you want to retrieve a property on an object that you don't\nknow for sure is private. (Properties beginning with an underscore '_'\nare considered private.)\n\nOn all newer browsers, you only need to use this method to retrieve\nproperties if the property might not be defined on the object and you want\nto respect the `unknownProperty` handler. Otherwise you can ignore this\nmethod.\n\nNote that if the object itself is `undefined`, this method will throw\nan error.",
       "itemtype": "method",
       "name": "get",
@@ -8123,8 +7477,8 @@
       "access": "private",
       "tagname": "Marks a property as tracked.\n\nBy default, a component's properties are expected to be static,\nmeaning you are not able to update them and have the template update accordingly.\nMarking a property as tracked means that when that property changes,\na rerender of the component is scheduled so the template is kept up to date.\n\nThere are two usages for the `@tracked` decorator, shown below.",
       "example": [
-        " No dependencies\n\nIf you don't pass an argument to `@tracked`, only changes to that property\nwill be tracked:\n\n```typescript\nimport Component, { tracked } from '@glimmer/component';\n\nexport default class MyComponent extends Component {\n  @tracked\n  remainingApples = 10\n}\n```\n\nWhen something changes the component's `remainingApples` property, the rerender\nwill be scheduled.",
-        " Dependents\n\nIn the case that you have a computed property that depends other\nproperties, you want to track both so that when one of the\ndependents change, a rerender is scheduled.\n\nIn the following example we have two properties,\n`eatenApples`, and `remainingApples`.\n\n```typescript\nimport Component, { tracked } from '@glimmer/component';\n\nconst totalApples = 100;\n\nexport default class MyComponent extends Component {\n  @tracked\n  eatenApples = 0\n\n  @tracked('eatenApples')\n  get remainingApples() {\n    return totalApples - this.eatenApples;\n  }\n\n  increment() {\n    this.eatenApples = this.eatenApples + 1;\n  }\n}\n```"
+        " No dependencies\n\nIf you don't pass an argument to `@tracked`, only changes to that property\nwill be tracked:\n\n```typescript\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\n\nexport default class MyComponent extends Component {\n  @tracked\n  remainingApples = 10\n}\n```\n\nWhen something changes the component's `remainingApples` property, the rerender\nwill be scheduled.",
+        " Dependents\n\nIn the case that you have a computed property that depends other\nproperties, you want to track both so that when one of the\ndependents change, a rerender is scheduled.\n\nIn the following example we have two properties,\n`eatenApples`, and `remainingApples`.\n\n```typescript\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\n\nconst totalApples = 100;\n\nexport default class MyComponent extends Component {\n  @tracked\n  eatenApples = 0\n\n  @tracked('eatenApples')\n  get remainingApples() {\n    return totalApples - this.eatenApples;\n  }\n\n  increment() {\n    this.eatenApples = this.eatenApples + 1;\n  }\n}\n```"
       ],
       "params": [
         {
@@ -9409,7 +8763,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 148,
+      "line": 147,
       "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",
@@ -9422,7 +8776,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 194,
+      "line": 193,
       "description": "The name of the template to use by default when rendering this routes\ntemplate.\n\n```app/routes/posts/list.js\nimport Route from '@ember/routing/route';\n\nexport default class extends Route {\n  templateName = 'posts/list'\n});\n```\n\n```app/routes/posts/index.js\nimport PostsList from '../posts/list';\n\nexport default class extends PostsList {};\n```\n\n```app/routes/posts/archived.js\nimport PostsList from '../posts/list';\n\nexport default class extends PostsList {};\n```",
       "itemtype": "property",
       "name": "templateName",
@@ -9436,7 +8790,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 227,
+      "line": 226,
       "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",
@@ -9450,7 +8804,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 250,
+      "line": 249,
       "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",
@@ -9463,7 +8817,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 281,
+      "line": 280,
       "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",
@@ -9476,7 +8830,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 295,
+      "line": 294,
       "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",
@@ -9489,7 +8843,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 310,
+      "line": 309,
       "description": "Sets the name for this route, including a fully resolved name for routes\ninside engines.",
       "access": "private",
       "tagname": "",
@@ -9507,7 +8861,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 323,
+      "line": 322,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -9517,7 +8871,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 354,
+      "line": 353,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -9527,7 +8881,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 363,
+      "line": 362,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -9537,7 +8891,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 371,
+      "line": 370,
       "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",
@@ -9560,7 +8914,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 450,
+      "line": 449,
       "description": "Serializes the query parameter key",
       "itemtype": "method",
       "name": "serializeQueryParamKey",
@@ -9578,7 +8932,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 461,
+      "line": 460,
       "description": "Serializes value of the query parameter based on defaultValueType",
       "itemtype": "method",
       "name": "serializeQueryParam",
@@ -9606,7 +8960,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 477,
+      "line": 476,
       "description": "Deserializes value of the query parameter based on defaultValueType",
       "itemtype": "method",
       "name": "deserializeQueryParam",
@@ -9634,7 +8988,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 493,
+      "line": 492,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -9644,7 +8998,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 502,
+      "line": 501,
       "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",
@@ -9673,7 +9027,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 529,
+      "line": 528,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -9683,7 +9037,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 540,
+      "line": 539,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -9694,7 +9048,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 553,
+      "line": 552,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -9704,7 +9058,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 564,
+      "line": 563,
       "description": "The `willTransition` action is fired at the beginning of any\nattempted transition with a `Transition` object as the sole\nargument. This action can be used for aborting, redirecting,\nor decorating the transition from the currently active routes.\n\nA good example is preventing navigation when a form is\nhalf-filled out:\n\n```app/routes/contact-form.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class ContactFormRoute extends Route {\n  @action\n  willTransition(transition) {\n    if (this.controller.get('userHasEnteredData')) {\n      this.controller.displayNavigationConfirm();\n      transition.abort();\n    }\n  }\n}\n```\n\nYou can also redirect elsewhere by calling\n`this.transitionTo('elsewhere')` from within `willTransition`.\nNote that `willTransition` will not be fired for the\nredirecting `transitionTo`, since `willTransition` doesn't\nfire when there is already a transition underway. If you want\nsubsequent `willTransition` actions to fire for the redirecting\ntransition, you must first explicitly call\n`transition.abort()`.\n\nTo allow the `willTransition` event to continue bubbling to the parent\nroute, use `return true;`. When the `willTransition` method has a\nreturn value of `true` then the parent route's `willTransition` method\nwill be fired, enabling \"bubbling\" behavior for the event.",
       "itemtype": "event",
       "name": "willTransition",
@@ -9723,7 +9077,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 608,
+      "line": 607,
       "description": "The `didTransition` action is fired after a transition has\nsuccessfully been completed. This occurs after the normal model\nhooks (`beforeModel`, `model`, `afterModel`, `setupController`)\nhave resolved. The `didTransition` action has no arguments,\nhowever, it can be useful for tracking page views or resetting\nstate on the controller.\n\n```app/routes/login.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class LoginRoute extends Route {\n  @action\n  didTransition() {\n    this.controller.get('errors.base').clear();\n    return true; // Bubble the didTransition event\n  }\n}\n```",
       "itemtype": "event",
       "name": "didTransition",
@@ -9735,7 +9089,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 634,
+      "line": 633,
       "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",
@@ -9759,7 +9113,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 668,
+      "line": 667,
       "description": "When attempting to transition into a route, any of the hooks\nmay return a promise that rejects, at which point an `error`\naction will be fired on the partially-entered routes, allowing\nfor per-route error handling logic, or shared error handling\nlogic defined on a parent route.\n\nHere is an example of an error handler that will be invoked\nfor rejected promises from the various hooks on the route,\nas well as any unhandled errors from child routes:\n\n```app/routes/admin.js\nimport { reject } from 'rsvp';\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class AdminRoute extends Route {\n  beforeModel() {\n    return reject('bad things!');\n  }\n\n  @action\n  error(error, transition) {\n    // Assuming we got here due to the error in `beforeModel`,\n    // we can expect that error === \"bad things!\",\n    // but a promise model rejecting would also\n    // call this hook, as would any errors encountered\n    // in `afterModel`.\n\n    // The `error` hook is also provided the failed\n    // `transition`, which can be stored and later\n    // `.retry()`d if desired.\n\n    this.transitionTo('login');\n  }\n}\n```\n\n`error` actions that bubble up all the way to `ApplicationRoute`\nwill fire a default error handler that logs the error. You can\nspecify your own global default error handler by overriding the\n`error` handler on `ApplicationRoute`:\n\n```app/routes/application.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class ApplicationRoute extends Route {\n  @action\n  error(error, transition) {\n    this.controllerFor('banner').displayError(error.message);\n  }\n}\n```",
       "itemtype": "event",
       "name": "error",
@@ -9783,7 +9137,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 729,
+      "line": 728,
       "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",
@@ -9795,7 +9149,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 749,
+      "line": 748,
       "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",
@@ -9807,7 +9161,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 769,
+      "line": 768,
       "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",
@@ -9826,7 +9180,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 780,
+      "line": 779,
       "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",
@@ -9845,7 +9199,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 791,
+      "line": 790,
       "description": "Transition the application into another route. The route may\nbe either a single route or route path:\n\n```javascript\nthis.transitionTo('blogPosts');\nthis.transitionTo('blogPosts.recentEntries');\n```\n\nOptionally supply a model for the route in question. The model\nwill be serialized into the URL using the `serialize` hook of\nthe route:\n\n```javascript\nthis.transitionTo('blogPost', aPost);\n```\n\nIf a literal is passed (such as a number or a string), it will\nbe treated as an identifier instead. In this case, the `model`\nhook of the route will be triggered:\n\n```javascript\nthis.transitionTo('blogPost', 1);\n```\n\nMultiple models will be applied last to first recursively up the\nroute tree.\n\n```app/routes.js\n// ...\n\nRouter.map(function() {\n  this.route('blogPost', { path:':blogPostId' }, function() {\n    this.route('blogComment', { path: ':blogCommentId' });\n  });\n});\n\nexport default Router;\n```\n\n```javascript\nthis.transitionTo('blogComment', aPost, aComment);\nthis.transitionTo('blogComment', 1, 13);\n```\n\nIt is also possible to pass a URL (a string that starts with a\n`/`).\n\n```javascript\nthis.transitionTo('/');\nthis.transitionTo('/blog/post/1/comment/13');\nthis.transitionTo('/blog/posts?sort=title');\n```\n\nAn options hash with a `queryParams` property may be provided as\nthe final argument to add query parameters to the destination URL.\n\n```javascript\nthis.transitionTo('blogPost', 1, {\n  queryParams: { showComments: 'true' }\n});\n\n// if you just want to transition the query parameters without changing the route\nthis.transitionTo({ queryParams: { sort: 'date' } });\n```\n\nSee also [replaceWith](#method_replaceWith).\n\nSimple Transition Example\n\n```app/routes.js\n// ...\n\nRouter.map(function() {\n  this.route('index');\n  this.route('secret');\n  this.route('fourOhFour', { path: '*:' });\n});\n\nexport default Router;\n```\n\n```app/routes/index.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class IndexRoute extends Route {\n  @action\n  moveToSecret(context) {\n    if (authorized()) {\n      this.transitionTo('secret', context);\n    } else {\n      this.transitionTo('fourOhFour');\n    }\n  }\n}\n```\n\nTransition to a nested route\n\n```app/router.js\n// ...\n\nRouter.map(function() {\n  this.route('articles', { path: '/articles' }, function() {\n    this.route('new');\n  });\n});\n\nexport default Router;\n```\n\n```app/routes/index.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class IndexRoute extends Route {\n  @action\n  transitionToNewArticle() {\n    this.transitionTo('articles.new');\n  }\n}\n```\n\nMultiple Models Example\n\n```app/router.js\n// ...\n\nRouter.map(function() {\n  this.route('index');\n\n  this.route('breakfast', { path: ':breakfastId' }, function() {\n    this.route('cereal', { path: ':cerealId' });\n  });\n});\n\nexport default Router;\n```\n\n```app/routes/index.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class IndexRoute extends Route {\n  @action\n  moveToChocolateCereal() {\n    let cereal = { cerealId: 'ChocolateYumminess' };\n    let breakfast = { breakfastId: 'CerealAndMilk' };\n\n    this.transitionTo('breakfast.cereal', breakfast, cereal);\n  }\n}\n```\n\nNested Route with Query String Example\n\n```app/routes.js\n// ...\n\nRouter.map(function() {\n  this.route('fruits', function() {\n    this.route('apples');\n  });\n});\n\nexport default Router;\n```\n\n```app/routes/index.js\nimport Route from '@ember/routing/route';\n\nexport default class IndexRoute extends Route {\n  @action\n  transitionToApples() {\n    this.transitionTo('fruits.apples', { queryParams: { color: 'red' } });\n  }\n}\n```",
       "itemtype": "method",
       "name": "transitionTo",
@@ -9883,7 +9237,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 989,
+      "line": 988,
       "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",
@@ -9907,7 +9261,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1011,
+      "line": 1010,
       "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",
@@ -9923,7 +9277,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1037,
+      "line": 1036,
       "description": "Transition into another route while replacing the current URL, if possible.\nThis will replace the current history entry instead of adding a new one.\nBeside that, it is identical to `transitionTo` in all other respects. See\n'transitionTo' for additional information regarding multiple models.\n\nExample\n\n```app/router.js\n// ...\n\nRouter.map(function() {\n  this.route('index');\n  this.route('secret');\n});\n\nexport default Router;\n```\n\n```app/routes/secret.js\nimport Route from '@ember/routing/route';\n\nexport default class SecretRoute Route {\n  afterModel() {\n    if (!authorized()){\n      this.replaceWith('index');\n    }\n  }\n}\n```",
       "itemtype": "method",
       "name": "replaceWith",
@@ -9957,7 +9311,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1084,
+      "line": 1083,
       "description": "This hook is the entry point for router.js",
       "access": "private",
       "tagname": "",
@@ -9968,7 +9322,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1164,
+      "line": 1163,
       "description": "This hook is the first of the route entry validation hooks\ncalled when an attempt is made to transition into a route\nor one of its children. It is called before `model` and\n`afterModel`, and is appropriate for cases when:\n\n1) A decision can be made to redirect elsewhere without\n   needing to resolve the model first.\n2) Any async operations need to occur first before the\n   model is attempted to be resolved.\n\nThis hook is provided the current `transition` attempt\nas a parameter, which can be used to `.abort()` the transition,\nsave it for a later `.retry()`, or retrieve values set\non it from a previous hook. You can also just call\n`this.transitionTo` to another route to implicitly\nabort the `transition`.\n\nYou can return a promise from this hook to pause the\ntransition until the promise resolves (or rejects). This could\nbe useful, for instance, for retrieving async code from\nthe server that is required to enter a route.",
       "itemtype": "method",
       "name": "beforeModel",
@@ -9991,7 +9345,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1198,
+      "line": 1197,
       "description": "This hook is called after this route's model has resolved.\nIt follows identical async/promise semantics to `beforeModel`\nbut is provided the route's resolved model in addition to\nthe `transition`, and is therefore suited to performing\nlogic that can only take place after the model has already\nresolved.\n\n```app/routes/posts.js\nimport Route from '@ember/routing/route';\n\nexport default class PostsRoute extends Route {\n  afterModel(posts, transition) {\n    if (posts.get('length') === 1) {\n      this.transitionTo('post.show', posts.get('firstObject'));\n    }\n  }\n}\n```\n\nRefer to documentation for `beforeModel` for a description\nof transition-pausing semantics when a promise is returned\nfrom this hook.",
       "itemtype": "method",
       "name": "afterModel",
@@ -10019,7 +9373,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1235,
+      "line": 1234,
       "description": "A hook you can implement to optionally redirect to another route.\n\nCalling `this.transitionTo` from inside of the `redirect` hook will\nabort the current transition (into the route that has implemented `redirect`).\n\n`redirect` and `afterModel` behave very similarly and are\ncalled almost at the same time, but they have an important\ndistinction when calling `this.transitionTo` to a child route\nof the current route. From `afterModel`, this new transition\ninvalidates the current transition, causing `beforeModel`,\n`model`, and `afterModel` hooks to be called again. But the\nsame transition started from `redirect` does _not_ invalidate\nthe current transition. In other words, by the time the `redirect`\nhook has been called, both the resolved model and the attempted\nentry into this route are considered fully validated.",
       "itemtype": "method",
       "name": "redirect",
@@ -10043,7 +9397,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1260,
+      "line": 1259,
       "description": "Called when the context is changed by router.js.",
       "access": "private",
       "tagname": "",
@@ -10054,7 +9408,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1270,
+      "line": 1269,
       "description": "A hook you can implement to convert the URL into the model for\nthis route.\n\n```app/router.js\n// ...\n\nRouter.map(function() {\n  this.route('post', { path: '/posts/:post_id' });\n});\n\nexport default Router;\n```\n\nThe model for the `post` route is `store.findRecord('post', params.post_id)`.\n\nBy default, if your route has a dynamic segment ending in `_id`:\n\n* The model class is determined from the segment (`post_id`'s\n  class is `App.Post`)\n* The find method is called on the model class with the value of\n  the dynamic segment.\n\nNote that for routes with dynamic segments, this hook is not always\nexecuted. If the route is entered through a transition (e.g. when\nusing the `link-to` Handlebars helper or the `transitionTo` method\nof routes), and a model context is already provided this hook\nis not called.\n\nA model context does not include a primitive string or number,\nwhich does cause the model hook to be called.\n\nRoutes without dynamic segments will always execute the model hook.\n\n```javascript\n// no dynamic segment, model hook always called\nthis.transitionTo('posts');\n\n// model passed in, so model hook not called\nthePost = store.findRecord('post', 1);\nthis.transitionTo('post', thePost);\n\n// integer passed in, model hook is called\nthis.transitionTo('post', 1);\n\n// model id passed in, model hook is called\n// useful for forcing the hook to execute\nthePost = store.findRecord('post', 1);\nthis.transitionTo('post', thePost.id);\n```\n\nThis hook follows the asynchronous/promise semantics\ndescribed in the documentation for `beforeModel`. In particular,\nif a promise returned from `model` fails, the error will be\nhandled by the `error` hook on `Route`.\n\nExample\n\n```app/routes/post.js\nimport Route from '@ember/routing/route';\n\nexport default class PostRoute extends Route {\n  model(params) {\n    return this.store.findRecord('post', params.post_id);\n  }\n}\n```",
       "itemtype": "method",
       "name": "model",
@@ -10082,7 +9436,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1379,
+      "line": 1378,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -10108,7 +9462,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1392,
+      "line": 1391,
       "itemtype": "method",
       "name": "findModel",
       "params": [
@@ -10130,7 +9484,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1403,
+      "line": 1402,
       "description": "A hook you can use to setup the controller for the current route.\n\nThis method is called with the controller for the current route and the\nmodel supplied by the `model` hook.\n\nBy default, the `setupController` hook sets the `model` property of\nthe controller to the specified `model` when it is not `undefined`.\n\nIf you implement the `setupController` hook in your Route, it will\nprevent this default behavior. If you want to preserve that behavior\nwhen implementing your `setupController` function, make sure to call\n`super`:\n\n```app/routes/photos.js\nimport Route from '@ember/routing/route';\n\nexport default class PhotosRoute extends Route {\n  model() {\n    return this.store.findAll('photo');\n  }\n\n  setupController(controller, model) {\n    super.setupController(controller, model);\n\n    this.controllerFor('application').set('showingPhotos', true);\n  }\n}\n```\n\nThe provided controller will be one resolved based on the name\nof this route.\n\nIf no explicit controller is defined, Ember will automatically create one.\n\nAs an example, consider the router:\n\n```app/router.js\n// ...\n\nRouter.map(function() {\n  this.route('post', { path: '/posts/:post_id' });\n});\n\nexport default Router;\n```\n\nIf you have defined a file for the post controller,\nthe framework will use it.\nIf it is not defined, a basic `Controller` instance would be used.",
       "example": [
         " Behavior of a basic Controller\n\n```app/routes/post.js\nimport Route from '@ember/routing/route';\n\nexport default class PostRoute extends Route {\n  setupController(controller, model) {\n    controller.set('model', model);\n  }\n});\n```"
@@ -10163,7 +9517,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1480,
+      "line": 1479,
       "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",
@@ -10186,7 +9540,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1526,
+      "line": 1525,
       "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",
@@ -10204,7 +9558,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1553,
+      "line": 1552,
       "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",
@@ -10227,7 +9581,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1624,
+      "line": 1623,
       "description": "`this[RENDER]` is used to render a template into a region of another template\n(indicated by an `{{outlet}}`).",
       "itemtype": "method",
       "name": "this[RENDER]",
@@ -10277,7 +9631,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1651,
+      "line": 1650,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -10287,7 +9641,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1664,
+      "line": 1663,
       "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 { inject as 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",
@@ -10302,7 +9656,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1714,
+      "line": 1713,
       "description": "Store property provides a hook for data persistence libraries to inject themselves.\n\nBy default, this store property provides the exact same functionality previously\nin the model hook.\n\nCurrently, the required interface is:\n\n`store.find(modelName, findArguments)`",
       "itemtype": "property",
       "name": "store",
@@ -10314,7 +9668,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1762,
+      "line": 1761,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -10324,7 +9678,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 1892,
+      "line": 1891,
       "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",
@@ -10348,7 +9702,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 2219,
+      "line": 2218,
       "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",
@@ -10376,7 +9730,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 2289,
+      "line": 2288,
       "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",
@@ -10389,7 +9743,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/route.ts",
-      "line": 2320,
+      "line": 2319,
       "description": "This action is called when one or more query params have changed. Bubbles.",
       "itemtype": "method",
       "name": "queryParamsDidChange",
@@ -10421,7 +9775,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 145,
+      "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",
@@ -10433,7 +9787,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 156,
+      "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 `auto` by the `locationType` setting of `/config/environment.js`",
       "itemtype": "property",
       "name": "location",
@@ -10448,7 +9802,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 212,
+      "line": 203,
       "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",
@@ -10465,7 +9819,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 562,
+      "line": 525,
       "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",
@@ -10476,7 +9830,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 684,
+      "line": 647,
       "description": "Transition the application into another route. The route may\nbe either a single route or route path:\n\nSee [transitionTo](/ember/release/classes/Route/methods/transitionTo?anchor=transitionTo) for more info.",
       "itemtype": "method",
       "name": "transitionTo",
@@ -10509,7 +9863,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 741,
+      "line": 704,
       "description": "Determines if the supplied route is currently active.",
       "itemtype": "method",
       "name": "isActive",
@@ -10530,7 +9884,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 753,
+      "line": 716,
       "description": "An alternative form of `isActive` that doesn't require\nmanual concatenation of the arguments into a single\narray.",
       "itemtype": "method",
       "name": "isActiveIntent",
@@ -10560,7 +9914,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 775,
+      "line": 738,
       "description": "Does this router instance have the given route.",
       "itemtype": "method",
       "name": "hasRoute",
@@ -10575,7 +9929,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 786,
+      "line": 749,
       "description": "Resets the state of the router by clearing the current route\nhandlers and deactivating them.",
       "access": "private",
       "tagname": "",
@@ -10586,7 +9940,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 894,
+      "line": 857,
       "description": "Serializes the given query params according to their QP meta information.",
       "access": "private",
       "tagname": "",
@@ -10613,7 +9967,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 921,
+      "line": 884,
       "description": "Serializes the value of a query parameter based on a type",
       "access": "private",
       "tagname": "",
@@ -10636,7 +9990,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 939,
+      "line": 902,
       "description": "Deserializes the given query params according to their QP meta information.",
       "access": "private",
       "tagname": "",
@@ -10663,7 +10017,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 964,
+      "line": 927,
       "description": "Deserializes the value of a query parameter based on a default type",
       "access": "private",
       "tagname": "",
@@ -10686,7 +10040,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 985,
+      "line": 948,
       "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": "",
@@ -10713,7 +10067,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1067,
+      "line": 1030,
       "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": "",
@@ -10750,7 +10104,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1094,
+      "line": 1057,
       "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": "",
@@ -10772,7 +10126,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1108,
+      "line": 1071,
       "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": "",
@@ -10794,7 +10148,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1173,
+      "line": 1136,
       "description": "Maps all query param keys to their fully scoped property name of the form\n`controllerName:propName`.",
       "access": "private",
       "tagname": "",
@@ -10826,7 +10180,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1215,
+      "line": 1178,
       "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": "",
@@ -10853,11 +10207,11 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1378,
+      "line": 1341,
       "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 { inject as 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",
-      "access": "public",
+      "access": "private",
       "tagname": "",
       "since": "1.2.0",
       "class": "EmberRouter",
@@ -10865,11 +10219,11 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1415,
+      "line": 1378,
       "description": "Handles notifying any listeners of an impending URL\nchange.\n\nTriggers the router level `willTransition` hook.",
       "itemtype": "method",
       "name": "willTransition",
-      "access": "public",
+      "access": "private",
       "tagname": "",
       "since": "1.11.0",
       "class": "EmberRouter",
@@ -10877,7 +10231,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1428,
+      "line": 1391,
       "description": "Represents the current URL.",
       "itemtype": "property",
       "name": "url",
@@ -10889,7 +10243,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1584,
+      "line": 1547,
       "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": "",
@@ -10914,7 +10268,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1603,
+      "line": 1566,
       "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": "",
@@ -10939,7 +10293,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1623,
+      "line": 1586,
       "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": "",
@@ -13540,7 +12894,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/target_action_support.js",
-      "line": 46,
+      "line": 41,
       "description": "Send an `action` with an `actionContext` to a `target`. The action, actionContext\nand target will be retrieved from properties of the object. For example:\n\n```javascript\nimport { alias } from '@ember/object/computed';\n\nApp.SaveButtonView = Ember.View.extend(Ember.TargetActionSupport, {\n  target: alias('controller'),\n  action: 'save',\n  actionContext: alias('context'),\n  click() {\n    this.triggerAction(); // Sends the `save` action, along with the current context\n                          // to the current controller\n  }\n});\n```\n\nThe `target`, `action`, and `actionContext` can be provided as properties of\nan optional object argument to `triggerAction` as well.\n\n```javascript\nApp.SaveButtonView = Ember.View.extend(Ember.TargetActionSupport, {\n  click() {\n    this.triggerAction({\n      action: 'save',\n      target: this.get('controller'),\n      actionContext: this.get('context')\n    }); // Sends the `save` action, along with the current context\n        // to the current controller\n  }\n});\n```\n\nThe `actionContext` defaults to the object you are mixing `TargetActionSupport` into.\nBut `target` and `action` must be specified either as properties or with the argument\nto `triggerAction`, or a combination:\n\n```javascript\nimport { alias } from '@ember/object/computed';\n\nApp.SaveButtonView = Ember.View.extend(Ember.TargetActionSupport, {\n  target: alias('controller'),\n  click() {\n    this.triggerAction({\n      action: 'save'\n    }); // Sends the `save` action, along with a reference to `this`,\n        // to the current controller\n  }\n});\n```",
       "itemtype": "method",
       "name": "triggerAction",
@@ -14213,7 +13567,6 @@
     {
       "file": "packages/@ember/-internals/utils/lib/guid.ts",
       "line": 8,
-      "description": "Previously we used `Ember.$.uuid`, however `$.uuid` has been removed from\njQuery master. We'll just bootstrap our own uuid now.",
       "access": "private",
       "tagname": "",
       "return": {
@@ -14225,7 +13578,7 @@
     },
     {
       "file": "packages/@ember/-internals/utils/lib/guid.ts",
-      "line": 17,
+      "line": 14,
       "description": "Generates a universally unique identifier. This method\nis used internally by Ember for assisting with\nthe generation of GUID's and other unique identifiers.",
       "access": "public",
       "tagname": "",
@@ -14238,7 +13591,7 @@
     },
     {
       "file": "packages/@ember/-internals/utils/lib/guid.ts",
-      "line": 29,
+      "line": 26,
       "description": "Prefix used for guids through out Ember.",
       "access": "private",
       "tagname": "",
@@ -14251,7 +13604,7 @@
     },
     {
       "file": "packages/@ember/-internals/utils/lib/guid.ts",
-      "line": 42,
+      "line": 39,
       "description": "A unique key used to assign guids and other private metadata to objects.\nIf you inspect an object in your browser debugger you will often see these.\nThey can be safely ignored.\n\nOn browsers that support it, these properties are added with enumeration\ndisabled so they won't show up when you iterate over your properties.",
       "access": "private",
       "tagname": "",
@@ -14264,7 +13617,7 @@
     },
     {
       "file": "packages/@ember/-internals/utils/lib/guid.ts",
-      "line": 58,
+      "line": 55,
       "description": "Generates a new guid, optionally saving the guid to the object that you\npass in. You will rarely need to use this method. Instead you should\ncall `guidFor(obj)`, which return an existing guid if available.",
       "access": "private",
       "tagname": "",
@@ -14294,7 +13647,7 @@
     },
     {
       "file": "packages/@ember/-internals/utils/lib/guid.ts",
-      "line": 86,
+      "line": 83,
       "description": "Returns a unique id for the object. If the object does not yet have a guid,\none will be assigned to it. You can call this on any object,\n`EmberObject`-based or not.\n\nYou can also use this method on DOM Element objects.",
       "access": "public",
       "tagname": "",
@@ -14481,153 +13834,6 @@
       "module": "ember",
       "namespace": "Ember"
     },
-    {
-      "file": "packages/@ember/-internals/views/lib/mixins/text_support.js",
-      "line": 143,
-      "description": "Whether the `keyUp` event that triggers an `action` to be sent continues\npropagating to other views.\n\nBy default, when the user presses the return key on their keyboard and\nthe text field has an `action` set, the action will be sent to the view's\ncontroller and the key event will stop propagating.\n\nIf you would like parent views to receive the `keyUp` event even after an\naction has been dispatched, set `bubbles` to true.",
-      "itemtype": "property",
-      "name": "bubbles",
-      "type": "Boolean",
-      "default": "false",
-      "access": "private",
-      "tagname": "",
-      "class": "Ember.TextSupport",
-      "module": "ember",
-      "namespace": "Ember"
-    },
-    {
-      "file": "packages/@ember/-internals/views/lib/mixins/text_support.js",
-      "line": 190,
-      "description": "Allows you to specify a controller action to invoke when either the `enter`\nkey is pressed or, in the case of the field being a textarea, when a newline\nis inserted. To use this method, give your field an `insert-newline`\nattribute. The value of that attribute should be the name of the action\nin your controller that you wish to invoke.\n\nFor an example on how to use the `insert-newline` attribute, please\nreference the example near the top of this file.",
-      "itemtype": "method",
-      "name": "insertNewline",
-      "params": [
-        {
-          "name": "event",
-          "description": "",
-          "type": "Event"
-        }
-      ],
-      "access": "private",
-      "tagname": "",
-      "class": "Ember.TextSupport",
-      "module": "ember",
-      "namespace": "Ember"
-    },
-    {
-      "file": "packages/@ember/-internals/views/lib/mixins/text_support.js",
-      "line": 209,
-      "description": "Allows you to specify a controller action to invoke when the escape button\nis pressed. To use this method, give your field an `escape-press`\nattribute. The value of that attribute should be the name of the action\nin your controller that you wish to invoke.\n\nFor an example on how to use the `escape-press` attribute, please reference\nthe example near the top of this file.",
-      "itemtype": "method",
-      "name": "cancel",
-      "params": [
-        {
-          "name": "event",
-          "description": "",
-          "type": "Event"
-        }
-      ],
-      "access": "private",
-      "tagname": "",
-      "class": "Ember.TextSupport",
-      "module": "ember",
-      "namespace": "Ember"
-    },
-    {
-      "file": "packages/@ember/-internals/views/lib/mixins/text_support.js",
-      "line": 226,
-      "description": "Allows you to specify a controller action to invoke when a field receives\nfocus. To use this method, give your field a `focus-in` attribute. The value\nof that attribute should be the name of the action in your controller\nthat you wish to invoke.\n\nFor an example on how to use the `focus-in` attribute, please reference the\nexample near the top of this file.",
-      "itemtype": "method",
-      "name": "focusIn",
-      "params": [
-        {
-          "name": "event",
-          "description": "",
-          "type": "Event"
-        }
-      ],
-      "access": "private",
-      "tagname": "",
-      "class": "Ember.TextSupport",
-      "module": "ember",
-      "namespace": "Ember"
-    },
-    {
-      "file": "packages/@ember/-internals/views/lib/mixins/text_support.js",
-      "line": 243,
-      "description": "Allows you to specify a controller action to invoke when a field loses\nfocus. To use this method, give your field a `focus-out` attribute. The value\nof that attribute should be the name of the action in your controller\nthat you wish to invoke.\n\nFor an example on how to use the `focus-out` attribute, please reference the\nexample near the top of this file.",
-      "itemtype": "method",
-      "name": "focusOut",
-      "params": [
-        {
-          "name": "event",
-          "description": "",
-          "type": "Event"
-        }
-      ],
-      "access": "private",
-      "tagname": "",
-      "class": "Ember.TextSupport",
-      "module": "ember",
-      "namespace": "Ember"
-    },
-    {
-      "file": "packages/@ember/-internals/views/lib/mixins/text_support.js",
-      "line": 261,
-      "description": "Allows you to specify a controller action to invoke when a key is pressed.\nTo use this method, give your field a `key-press` attribute. The value of\nthat attribute should be the name of the action in your controller you\nthat wish to invoke.\n\nFor an example on how to use the `key-press` attribute, please reference the\nexample near the top of this file.",
-      "itemtype": "method",
-      "name": "keyPress",
-      "params": [
-        {
-          "name": "event",
-          "description": "",
-          "type": "Event"
-        }
-      ],
-      "access": "private",
-      "tagname": "",
-      "class": "Ember.TextSupport",
-      "module": "ember",
-      "namespace": "Ember"
-    },
-    {
-      "file": "packages/@ember/-internals/views/lib/mixins/text_support.js",
-      "line": 278,
-      "description": "Allows you to specify a controller action to invoke when a key-up event is\nfired. To use this method, give your field a `key-up` attribute. The value\nof that attribute should be the name of the action in your controller\nthat you wish to invoke.\n\nFor an example on how to use the `key-up` attribute, please reference the\nexample near the top of this file.",
-      "itemtype": "method",
-      "name": "keyUp",
-      "params": [
-        {
-          "name": "event",
-          "description": "",
-          "type": "Event"
-        }
-      ],
-      "access": "private",
-      "tagname": "",
-      "class": "Ember.TextSupport",
-      "module": "ember",
-      "namespace": "Ember"
-    },
-    {
-      "file": "packages/@ember/-internals/views/lib/mixins/text_support.js",
-      "line": 296,
-      "description": "Allows you to specify a controller action to invoke when a key-down event is\nfired. To use this method, give your field a `key-down` attribute. The value\nof that attribute should be the name of the action in your controller that\nyou wish to invoke.\n\nFor an example on how to use the `key-down` attribute, please reference the\nexample near the top of this file.",
-      "itemtype": "method",
-      "name": "keyDown",
-      "params": [
-        {
-          "name": "event",
-          "description": "",
-          "type": "Event"
-        }
-      ],
-      "access": "private",
-      "tagname": "",
-      "class": "Ember.TextSupport",
-      "module": "ember",
-      "namespace": "Ember"
-    },
     {
       "file": "packages/@ember/-internals/views/lib/mixins/view_support.js",
       "line": 12,
@@ -14719,8 +13925,8 @@
       "params": [
         {
           "name": "A",
-          "description": "selector, element, HTML string, or jQuery object",
-          "type": "String|DOMElement|jQuery"
+          "description": "selector, element, HTML string",
+          "type": "String|DOMElement"
         }
       ],
       "return": {
@@ -14839,7 +14045,7 @@
     {
       "file": "packages/@ember/-internals/views/lib/mixins/view_support.js",
       "line": 346,
-      "description": "Tag name for the view's outer element. The tag name is only used when an\nelement is first created. If you change the `tagName` for an element, you\nmust destroy and recreate the view element.\n\nBy default, the render buffer will use a `<div>` tag for views.\n\nIf the tagName is `''`, the view will be tagless, with no outer element.\nComponent properties that depend on the presence of an outer element, such\nas `classNameBindings` and `attributeBindings`, do not work with tagless\ncomponents. Tagless components cannot implement methods to handle events,\nand have no associated jQuery object to return with `$()`.",
+      "description": "Tag name for the view's outer element. The tag name is only used when an\nelement is first created. If you change the `tagName` for an element, you\nmust destroy and recreate the view element.\n\nBy default, the render buffer will use a `<div>` tag for views.\n\nIf the tagName is `''`, the view will be tagless, with no outer element.\nComponent properties that depend on the presence of an outer element, such\nas `classNameBindings` and `attributeBindings`, do not work with tagless\ncomponents. Tagless components cannot implement methods to handle events,\nand their `element` property has a `null` value.",
       "itemtype": "property",
       "name": "tagName",
       "type": "String",
@@ -15203,7 +14409,7 @@
     {
       "file": "packages/@ember/application/lib/application.js",
       "line": 185,
-      "description": "The root DOM element of the Application. This can be specified as an\nelement or a\n[jQuery-compatible selector string](http://api.jquery.com/category/selectors/).\n\nThis is the element that will be passed to the Application's,\n`eventDispatcher`, which sets up the listeners for event delegation. Every\nview in your application should be a child of the element you specify here.",
+      "description": "The root DOM element of the Application. This can be specified as an\nelement or a [selector string](https://developer.mozilla.org/en-US/docs/Learn/CSS/Building_blocks/Selectors#reference_table_of_selectors).\n\nThis is the element that will be passed to the Application's,\n`eventDispatcher`, which sets up the listeners for event delegation. Every\nview in your application should be a child of the element you specify here.",
       "itemtype": "property",
       "name": "rootElement",
       "type": "DOMElement",
@@ -15215,7 +14421,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.js",
-      "line": 201,
+      "line": 200,
       "itemtype": "property",
       "name": "_document",
       "type": "Document | null",
@@ -15227,7 +14433,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.js",
-      "line": 210,
+      "line": 209,
       "description": "The `Ember.EventDispatcher` responsible for delegating events to this\napplication's views.\n\nThe event dispatcher is created by the application at initialization time\nand sets up event listeners on the DOM element described by the\napplication's `rootElement` property.\n\nSee the documentation for `Ember.EventDispatcher` for more information.",
       "itemtype": "property",
       "name": "eventDispatcher",
@@ -15240,7 +14446,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.js",
-      "line": 227,
+      "line": 226,
       "description": "The DOM events for which the event dispatcher should listen.\n\nBy default, the application's `Ember.EventDispatcher` listens\nfor a set of standard DOM events, such as `mousedown` and\n`keyup`, and delegates them to your application's `Ember.View`\ninstances.\n\nIf you would like additional bubbling events to be delegated to your\nviews, set your `Application`'s `customEvents` property\nto a hash containing the DOM event name as the key and the\ncorresponding view method name as the value. Setting an event to\na value of `null` will prevent a default event listener from being\nadded for that event.\n\nTo add new events to be listened to:\n\n```app/app.js\nimport Application from '@ember/application';\n\nlet App = Application.extend({\n  customEvents: {\n    // add support for the paste event\n    paste: 'paste'\n  }\n});\n```\n\nTo prevent default events from being listened to:\n\n```app/app.js\nimport Application from '@ember/application';\n\nlet App = Application.extend({\n  customEvents: {\n    // remove support for mouseenter / mouseleave events\n    mouseenter: null,\n    mouseleave: null\n  }\n});\n```",
       "itemtype": "property",
       "name": "customEvents",
@@ -15253,7 +14459,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.js",
-      "line": 275,
+      "line": 274,
       "description": "Whether the application should automatically start routing and render\ntemplates to the `rootElement` on DOM ready. While default by true,\nother environments such as FastBoot or a testing harness can set this\nproperty to `false` and control the precise timing and behavior of the boot\nprocess.",
       "itemtype": "property",
       "name": "autoboot",
@@ -15266,7 +14472,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.js",
-      "line": 289,
+      "line": 288,
       "description": "Whether the application should be configured for the legacy \"globals mode\".\nUnder this mode, the Application object serves as a global namespace for all\nclasses.\n\n```javascript\nimport Application from '@ember/application';\nimport Component from '@ember/component';\n\nlet App = Application.create({\n  ...\n});\n\nApp.Router.reopen({\n  location: 'none'\n});\n\nApp.Router.map({\n  ...\n});\n\nApp.MyComponent = Component.extend({\n  ...\n});\n```\n\nThis flag also exposes other internal APIs that assumes the existence of\na special \"default instance\", like `App.__container__.lookup(...)`.\n\nThis option is currently not configurable, its value is derived from\nthe `autoboot` flag – disabling `autoboot` also implies opting-out of\nglobals mode support, although they are ultimately orthogonal concerns.\n\nSome of the global modes features are already deprecated in 1.x. The\nexistence of this flag is to untangle the globals mode code paths from\nthe autoboot code paths, so that these legacy features can be reviewed\nfor deprecation/removal separately.\n\nForcing the (autoboot=true, _globalsMode=false) here and running the tests\nwould reveal all the places where we are still relying on these legacy\nbehavior internally (mostly just tests).",
       "itemtype": "property",
       "name": "_globalsMode",
@@ -15279,7 +14485,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.js",
-      "line": 338,
+      "line": 337,
       "description": "An array of application instances created by `buildInstance()`. Used\ninternally to ensure that all instances get destroyed.",
       "itemtype": "property",
       "name": "_applicationInstances",
@@ -15292,7 +14498,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.js",
-      "line": 378,
+      "line": 377,
       "description": "Create an ApplicationInstance for this application.",
       "access": "public",
       "tagname": "",
@@ -15307,7 +14513,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.js",
-      "line": 401,
+      "line": 400,
       "description": "Start tracking an ApplicationInstance for this application.\nUsed when the ApplicationInstance is created.",
       "access": "private",
       "tagname": "",
@@ -15318,7 +14524,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.js",
-      "line": 412,
+      "line": 411,
       "description": "Stop tracking an ApplicationInstance for this application.\nUsed when the ApplicationInstance is about to be destroyed.",
       "access": "private",
       "tagname": "",
@@ -15329,7 +14535,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.js",
-      "line": 423,
+      "line": 422,
       "description": "Enable the legacy globals mode by allowing this application to act\nas a global namespace. See the docs on the `_globalsMode` property\nfor details.\n\nMost of these features are already deprecated in 1.x, so we can\nstop using them internally and try to remove them.",
       "access": "private",
       "tagname": "",
@@ -15340,7 +14546,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.js",
-      "line": 467,
+      "line": 466,
       "description": "Automatically kick-off the boot process for the application once the\nDOM has become ready.\n\nThe initialization itself is scheduled on the actions queue which\nensures that code-loading finishes before booting.\n\nIf you are asynchronously loading code, you should call `deferReadiness()`\nto defer booting, and then call `advanceReadiness()` once all of your code\nhas finished loading.",
       "access": "private",
       "tagname": "",
@@ -15351,7 +14557,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.js",
-      "line": 494,
+      "line": 493,
       "description": "This is the autoboot flow:\n\n1. Boot the app by calling `this.boot()`\n2. Create an instance (or use the `__deprecatedInstance__` in globals mode)\n3. Boot the instance by calling `instance.boot()`\n4. Invoke the `App.ready()` callback\n5. Kick-off routing on the instance\n\nIdeally, this is all we would need to do:\n\n```javascript\n_autoBoot() {\n  this.boot().then(() => {\n    let instance = (this._globalsMode) ? this.__deprecatedInstance__ : this.buildInstance();\n    return instance.boot();\n  }).then((instance) => {\n    App.ready();\n    instance.startRouting();\n  });\n}\n```\n\nUnfortunately, we cannot actually write this because we need to participate\nin the \"synchronous\" boot process. While the code above would work fine on\nthe initial boot (i.e. DOM ready), when `App.reset()` is called, we need to\nboot a new instance synchronously (see the documentation on `_bootSync()`\nfor details).\n\nBecause of this restriction, the actual logic of this method is located\ninside `didBecomeReady()`.",
       "access": "private",
       "tagname": "",
@@ -15362,8 +14568,8 @@
     },
     {
       "file": "packages/@ember/application/lib/application.js",
-      "line": 539,
-      "description": "Use this to defer readiness until some condition is true.\n\nExample:\n\n```javascript\nimport Application from '@ember/application';\n\nlet App = Application.create();\n\nApp.deferReadiness();\n\n// $ is a reference to the jQuery object/function\nimport $ from 'jquery;\n\n$.getJSON('/auth-token', function(token) {\n  App.token = token;\n  App.advanceReadiness();\n});\n```\n\nThis allows you to perform asynchronous setup logic and defer\nbooting your application until the setup has finished.\n\nHowever, if the setup requires a loading UI, it might be better\nto use the router for this purpose.",
+      "line": 538,
+      "description": "Use this to defer readiness until some condition is true.\n\nExample:\n\n```javascript\nimport Application from '@ember/application';\n\nlet App = Application.create();\n\nApp.deferReadiness();\n\nfetch('/auth-token')\n.then(response => response.json())\n.then(data => {\n  App.token = data.token;\n  App.advanceReadiness();\n});\n```\n\nThis allows you to perform asynchronous setup logic and defer\nbooting your application until the setup has finished.\n\nHowever, if the setup requires a loading UI, it might be better\nto use the router for this purpose.",
       "itemtype": "method",
       "name": "deferReadiness",
       "access": "public",
@@ -15373,7 +14579,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.js",
-      "line": 590,
+      "line": 588,
       "description": "Call `advanceReadiness` after any asynchronous setup logic has completed.\nEach call to `deferReadiness` must be matched by a call to `advanceReadiness`\nor the application will never become ready and routing will not begin.",
       "itemtype": "method",
       "name": "advanceReadiness",
@@ -15387,7 +14593,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.js",
-      "line": 627,
+      "line": 625,
       "description": "Initialize the application and return a promise that resolves with the `Application`\nobject when the boot process is complete.\n\nRun any application initializers and run the application load hook. These hooks may\nchoose to defer readiness. For example, an authentication hook might want to defer\nreadiness until the auth token has been retrieved.\n\nBy default, this method is called automatically on \"DOM ready\"; however, if autoboot\nis disabled, this is automatically called when the first application instance is\ncreated via `visit`.",
       "access": "public",
       "tagname": "",
@@ -15402,7 +14608,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.js",
-      "line": 665,
+      "line": 663,
       "description": "Unfortunately, a lot of existing code assumes the booting process is\n\"synchronous\". Specifically, a lot of tests assumes the last call to\n`app.advanceReadiness()` or `app.reset()` will result in the app being\nfully-booted when the current runloop completes.\n\nWe would like new code (like the `visit` API) to stop making this assumption,\nso we created the asynchronous version above that returns a promise. But until\nwe have migrated all the code, we would have to expose this method for use\n*internally* in places where we need to boot an app \"synchronously\".",
       "access": "private",
       "tagname": "",
@@ -15411,7 +14617,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.js",
-      "line": 704,
+      "line": 702,
       "description": "Reset the application. This is typically used only in tests. It cleans up\nthe application in the following order:\n\n1. Deactivate existing routes\n2. Destroy all objects in the container\n3. Create a new application container\n4. Re-route to the existing url\n\nTypical Example:\n\n```javascript\nimport Application from '@ember/application';\nlet App;\n\nrun(function() {\n  App = Application.create();\n});\n\nmodule('acceptance test', {\n  setup: function() {\n    App.reset();\n  }\n});\n\ntest('first test', function() {\n  // App is freshly reset\n});\n\ntest('second test', function() {\n  // App is again freshly reset\n});\n```\n\nAdvanced Example:\n\nOccasionally you may want to prevent the app from initializing during\nsetup. This could enable extra configuration, or enable asserting prior\nto the app becoming ready.\n\n```javascript\nimport Application from '@ember/application';\nlet App;\n\nrun(function() {\n  App = Application.create();\n});\n\nmodule('acceptance test', {\n  setup: function() {\n    run(function() {\n      App.reset();\n      App.deferReadiness();\n    });\n  }\n});\n\ntest('first test', function() {\n  ok(true, 'something before app is initialized');\n\n  run(function() {\n    App.advanceReadiness();\n  });\n\n  ok(true, 'something after app is initialized');\n});\n```",
       "itemtype": "method",
       "name": "reset",
@@ -15422,7 +14628,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.js",
-      "line": 807,
+      "line": 805,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -15432,7 +14638,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.js",
-      "line": 857,
+      "line": 855,
       "description": "Called when the Application has become ready, immediately before routing\nbegins. The call will be delayed until the DOM has become ready.",
       "itemtype": "event",
       "name": "ready",
@@ -15443,8 +14649,8 @@
     },
     {
       "file": "packages/@ember/application/lib/application.js",
-      "line": 882,
-      "description": "Boot a new instance of `ApplicationInstance` for the current\napplication and navigate it to the given `url`. Returns a `Promise` that\nresolves with the instance when the initial routing and rendering is\ncomplete, or rejects with any error that occurred during the boot process.\n\nWhen `autoboot` is disabled, calling `visit` would first cause the\napplication to boot, which runs the application initializers.\n\nThis method also takes a hash of boot-time configuration options for\ncustomizing the instance's behavior. See the documentation on\n`ApplicationInstance.BootOptions` for details.\n\n`ApplicationInstance.BootOptions` is an interface class that exists\npurely to document the available options; you do not need to construct it\nmanually. Simply pass a regular JavaScript object containing of the\ndesired options:\n\n```javascript\nMyApp.visit(\"/\", { location: \"none\", rootElement: \"#container\" });\n```\n\n### Supported Scenarios\n\nWhile the `BootOptions` class exposes a large number of knobs, not all\ncombinations of them are valid; certain incompatible combinations might\nresult in unexpected behavior.\n\nFor example, booting the instance in the full browser environment\nwhile specifying a foreign `document` object (e.g. `{ isBrowser: true,\ndocument: iframe.contentDocument }`) does not work correctly today,\nlargely due to Ember's jQuery dependency.\n\nCurrently, there are three officially supported scenarios/configurations.\nUsages outside of these scenarios are not guaranteed to work, but please\nfeel free to file bug reports documenting your experience and any issues\nyou encountered to help expand support.\n\n#### Browser Applications (Manual Boot)\n\nThe setup is largely similar to how Ember works out-of-the-box. Normally,\nEmber will boot a default instance for your Application on \"DOM ready\".\nHowever, you can customize this behavior by disabling `autoboot`.\n\nFor example, this allows you to render a miniture demo of your application\ninto a specific area on your marketing website:\n\n```javascript\nimport MyApp from 'my-app';\n\n$(function() {\n  let App = MyApp.create({ autoboot: false });\n\n  let options = {\n    // Override the router's location adapter to prevent it from updating\n    // the URL in the address bar\n    location: 'none',\n\n    // Override the default `rootElement` on the app to render into a\n    // specific `div` on the page\n    rootElement: '#demo'\n  };\n\n  // Start the app at the special demo URL\n  App.visit('/demo', options);\n});\n```\n\nOr perhaps you might want to boot two instances of your app on the same\npage for a split-screen multiplayer experience:\n\n```javascript\nimport MyApp from 'my-app';\n\n$(function() {\n  let App = MyApp.create({ autoboot: false });\n\n  let sessionId = MyApp.generateSessionID();\n\n  let player1 = App.visit(`/matches/join?name=Player+1&session=${sessionId}`, { rootElement: '#left', location: 'none' });\n  let player2 = App.visit(`/matches/join?name=Player+2&session=${sessionId}`, { rootElement: '#right', location: 'none' });\n\n  Promise.all([player1, player2]).then(() => {\n    // Both apps have completed the initial render\n    $('#loading').fadeOut();\n  });\n});\n```\n\nDo note that each app instance maintains their own registry/container, so\nthey will run in complete isolation by default.\n\n#### Server-Side Rendering (also known as FastBoot)\n\nThis setup allows you to run your Ember app in a server environment using\nNode.js and render its content into static HTML for SEO purposes.\n\n```javascript\nconst HTMLSerializer = new SimpleDOM.HTMLSerializer(SimpleDOM.voidMap);\n\nfunction renderURL(url) {\n  let dom = new SimpleDOM.Document();\n  let rootElement = dom.body;\n  let options = { isBrowser: false, document: dom, rootElement: rootElement };\n\n  return MyApp.visit(options).then(instance => {\n    try {\n      return HTMLSerializer.serialize(rootElement.firstChild);\n    } finally {\n      instance.destroy();\n    }\n  });\n}\n```\n\nIn this scenario, because Ember does not have access to a global `document`\nobject in the Node.js environment, you must provide one explicitly. In practice,\nin the non-browser environment, the stand-in `document` object only needs to\nimplement a limited subset of the full DOM API. The `SimpleDOM` library is known\nto work.\n\nSince there is no access to jQuery in the non-browser environment, you must also\nspecify a DOM `Element` object in the same `document` for the `rootElement` option\n(as opposed to a selector string like `\"body\"`).\n\nSee the documentation on the `isBrowser`, `document` and `rootElement` properties\non `ApplicationInstance.BootOptions` for details.\n\n#### Server-Side Resource Discovery\n\nThis setup allows you to run the routing layer of your Ember app in a server\nenvironment using Node.js and completely disable rendering. This allows you\nto simulate and discover the resources (i.e. AJAX requests) needed to fulfill\na given request and eagerly \"push\" these resources to the client.\n\n```app/initializers/network-service.js\nimport BrowserNetworkService from 'app/services/network/browser';\nimport NodeNetworkService from 'app/services/network/node';\n\n// Inject a (hypothetical) service for abstracting all AJAX calls and use\n// the appropriate implementation on the client/server. This also allows the\n// server to log all the AJAX calls made during a particular request and use\n// that for resource-discovery purpose.\n\nexport function initialize(application) {\n  if (window) { // browser\n    application.register('service:network', BrowserNetworkService);\n  } else { // node\n    application.register('service:network', NodeNetworkService);\n  }\n};\n\nexport default {\n  name: 'network-service',\n  initialize: initialize\n};\n```\n\n```app/routes/post.js\nimport Route from '@ember/routing/route';\nimport { inject as service } from '@ember/service';\n\n// An example of how the (hypothetical) service is used in routes.\n\nexport default class IndexRoute extends Route {\n  @service network;\n\n  model(params) {\n    return this.network.fetch(`/api/posts/${params.post_id}.json`);\n  }\n\n  afterModel(post) {\n    if (post.isExternalContent) {\n      return this.network.fetch(`/api/external/?url=${post.externalURL}`);\n    } else {\n      return post;\n    }\n  }\n}\n```\n\n```javascript\n// Finally, put all the pieces together\n\nfunction discoverResourcesFor(url) {\n  return MyApp.visit(url, { isBrowser: false, shouldRender: false }).then(instance => {\n    let networkService = instance.lookup('service:network');\n    return networkService.requests; // => { \"/api/posts/123.json\": \"...\" }\n  });\n}\n```",
+      "line": 880,
+      "description": "Boot a new instance of `ApplicationInstance` for the current\napplication and navigate it to the given `url`. Returns a `Promise` that\nresolves with the instance when the initial routing and rendering is\ncomplete, or rejects with any error that occurred during the boot process.\n\nWhen `autoboot` is disabled, calling `visit` would first cause the\napplication to boot, which runs the application initializers.\n\nThis method also takes a hash of boot-time configuration options for\ncustomizing the instance's behavior. See the documentation on\n`ApplicationInstance.BootOptions` for details.\n\n`ApplicationInstance.BootOptions` is an interface class that exists\npurely to document the available options; you do not need to construct it\nmanually. Simply pass a regular JavaScript object containing of the\ndesired options:\n\n```javascript\nMyApp.visit(\"/\", { location: \"none\", rootElement: \"#container\" });\n```\n\n### Supported Scenarios\n\nWhile the `BootOptions` class exposes a large number of knobs, not all\ncombinations of them are valid; certain incompatible combinations might\nresult in unexpected behavior.\n\nFor example, booting the instance in the full browser environment\nwhile specifying a foreign `document` object (e.g. `{ isBrowser: true,\ndocument: iframe.contentDocument }`) does not work correctly today,\nlargely due to Ember's jQuery dependency.\n\nCurrently, there are three officially supported scenarios/configurations.\nUsages outside of these scenarios are not guaranteed to work, but please\nfeel free to file bug reports documenting your experience and any issues\nyou encountered to help expand support.\n\n#### Browser Applications (Manual Boot)\n\nThe setup is largely similar to how Ember works out-of-the-box. Normally,\nEmber will boot a default instance for your Application on \"DOM ready\".\nHowever, you can customize this behavior by disabling `autoboot`.\n\nFor example, this allows you to render a miniture demo of your application\ninto a specific area on your marketing website:\n\n```javascript\nimport MyApp from 'my-app';\n\n$(function() {\n  let App = MyApp.create({ autoboot: false });\n\n  let options = {\n    // Override the router's location adapter to prevent it from updating\n    // the URL in the address bar\n    location: 'none',\n\n    // Override the default `rootElement` on the app to render into a\n    // specific `div` on the page\n    rootElement: '#demo'\n  };\n\n  // Start the app at the special demo URL\n  App.visit('/demo', options);\n});\n```\n\nOr perhaps you might want to boot two instances of your app on the same\npage for a split-screen multiplayer experience:\n\n```javascript\nimport MyApp from 'my-app';\n\n$(function() {\n  let App = MyApp.create({ autoboot: false });\n\n  let sessionId = MyApp.generateSessionID();\n\n  let player1 = App.visit(`/matches/join?name=Player+1&session=${sessionId}`, { rootElement: '#left', location: 'none' });\n  let player2 = App.visit(`/matches/join?name=Player+2&session=${sessionId}`, { rootElement: '#right', location: 'none' });\n\n  Promise.all([player1, player2]).then(() => {\n    // Both apps have completed the initial render\n    $('#loading').fadeOut();\n  });\n});\n```\n\nDo note that each app instance maintains their own registry/container, so\nthey will run in complete isolation by default.\n\n#### Server-Side Rendering (also known as FastBoot)\n\nThis setup allows you to run your Ember app in a server environment using\nNode.js and render its content into static HTML for SEO purposes.\n\n```javascript\nconst HTMLSerializer = new SimpleDOM.HTMLSerializer(SimpleDOM.voidMap);\n\nfunction renderURL(url) {\n  let dom = new SimpleDOM.Document();\n  let rootElement = dom.body;\n  let options = { isBrowser: false, document: dom, rootElement: rootElement };\n\n  return MyApp.visit(options).then(instance => {\n    try {\n      return HTMLSerializer.serialize(rootElement.firstChild);\n    } finally {\n      instance.destroy();\n    }\n  });\n}\n```\n\nIn this scenario, because Ember does not have access to a global `document`\nobject in the Node.js environment, you must provide one explicitly. In practice,\nin the non-browser environment, the stand-in `document` object only needs to\nimplement a limited subset of the full DOM API. The `SimpleDOM` library is known\nto work.\n\nSince there is no DOM access in the non-browser environment, you must also\nspecify a DOM `Element` object in the same `document` for the `rootElement` option\n(as opposed to a selector string like `\"body\"`).\n\nSee the documentation on the `isBrowser`, `document` and `rootElement` properties\non `ApplicationInstance.BootOptions` for details.\n\n#### Server-Side Resource Discovery\n\nThis setup allows you to run the routing layer of your Ember app in a server\nenvironment using Node.js and completely disable rendering. This allows you\nto simulate and discover the resources (i.e. AJAX requests) needed to fulfill\na given request and eagerly \"push\" these resources to the client.\n\n```app/initializers/network-service.js\nimport BrowserNetworkService from 'app/services/network/browser';\nimport NodeNetworkService from 'app/services/network/node';\n\n// Inject a (hypothetical) service for abstracting all AJAX calls and use\n// the appropriate implementation on the client/server. This also allows the\n// server to log all the AJAX calls made during a particular request and use\n// that for resource-discovery purpose.\n\nexport function initialize(application) {\n  if (window) { // browser\n    application.register('service:network', BrowserNetworkService);\n  } else { // node\n    application.register('service:network', NodeNetworkService);\n  }\n};\n\nexport default {\n  name: 'network-service',\n  initialize: initialize\n};\n```\n\n```app/routes/post.js\nimport Route from '@ember/routing/route';\nimport { inject as service } from '@ember/service';\n\n// An example of how the (hypothetical) service is used in routes.\n\nexport default class IndexRoute extends Route {\n  @service network;\n\n  model(params) {\n    return this.network.fetch(`/api/posts/${params.post_id}.json`);\n  }\n\n  afterModel(post) {\n    if (post.isExternalContent) {\n      return this.network.fetch(`/api/external/?url=${post.externalURL}`);\n    } else {\n      return post;\n    }\n  }\n}\n```\n\n```javascript\n// Finally, put all the pieces together\n\nfunction discoverResourcesFor(url) {\n  return MyApp.visit(url, { isBrowser: false, shouldRender: false }).then(instance => {\n    let networkService = instance.lookup('service:network');\n    return networkService.requests; // => { \"/api/posts/123.json\": \"...\" }\n  });\n}\n```",
       "access": "public",
       "tagname": "",
       "itemtype": "method",
@@ -15470,7 +14676,7 @@
     },
     {
       "file": "packages/@ember/application/lib/application.js",
-      "line": 1103,
+      "line": 1101,
       "description": "This creates a registry with the default Ember naming conventions.\n\nIt also configures the registry:\n\n* registered views are created every time they are looked up (they are\n  not singletons)\n* registered templates are not factories; the registered value is\n  returned directly.\n* the router receives the application as its `namespace` property\n* all controllers receive the router as their `target` and `controllers`\n  properties\n* all controllers receive the application as their `namespace` property\n* the application view receives the application controller as its\n  `controller` property\n* the application view receives the application template as its\n  `defaultTemplate` property",
       "itemtype": "method",
       "name": "buildRegistry",
@@ -15797,7 +15003,7 @@
     },
     {
       "file": "packages/@ember/canary-features/index.ts",
-      "line": 37,
+      "line": 36,
       "description": "Determine whether the specified `feature` is enabled. Used by Ember's\nbuild tools to exclude experimental features from beta/stable builds.\n\nYou can define the following configuration options:\n\n* `EmberENV.ENABLE_OPTIONAL_FEATURES` - enable any features that have not been explicitly\n  enabled/disabled.",
       "itemtype": "method",
       "name": "isEnabled",
@@ -16474,7 +15680,7 @@
     {
       "file": "packages/@ember/engine/index.js",
       "line": 305,
-      "description": "Instance initializers run after all initializers have run. Because\ninstance initializers run after the app is fully set up. We have access\nto the store, container, and other items. However, these initializers run\nafter code has loaded and are not allowed to defer readiness.\n\nInstance initializer receives an object which has the following attributes:\n`name`, `before`, `after`, `initialize`. The only required attribute is\n`initialize`, all others are optional.\n\n* `name` allows you to specify under which name the instanceInitializer is\nregistered. This must be a unique name, as trying to register two\ninstanceInitializer with the same name will result in an error.\n\n```app/initializer/named-instance-initializer.js\nimport { debug } from '@ember/debug';\n\nexport function initialize() {\n  debug('Running named-instance-initializer!');\n}\n\nexport default {\n  name: 'named-instance-initializer',\n  initialize\n};\n```\n\n* `before` and `after` are used to ensure that this initializer is ran prior\nor after the one identified by the value. This value can be a single string\nor an array of strings, referencing the `name` of other initializers.\n\n* See Application.initializer for discussion on the usage of before\nand after.\n\nExample instanceInitializer to preload data into the store.\n\n```app/initializer/preload-data.js\nimport $ from 'jquery';\n\nexport function initialize(application) {\n    var userConfig, userConfigEncoded, store;\n    // We have a HTML escaped JSON representation of the user's basic\n    // configuration generated server side and stored in the DOM of the main\n    // index.html file. This allows the app to have access to a set of data\n    // without making any additional remote calls. Good for basic data that is\n    // needed for immediate rendering of the page. Keep in mind, this data,\n    // like all local models and data can be manipulated by the user, so it\n    // should not be relied upon for security or authorization.\n\n    // Grab the encoded data from the meta tag\n    userConfigEncoded = $('head meta[name=app-user-config]').attr('content');\n\n    // Unescape the text, then parse the resulting JSON into a real object\n    userConfig = JSON.parse(unescape(userConfigEncoded));\n\n    // Lookup the store\n    store = application.lookup('service:store');\n\n    // Push the encoded JSON into the store\n    store.pushPayload(userConfig);\n}\n\nexport default {\n  name: 'named-instance-initializer',\n  initialize\n};\n```",
+      "description": "Instance initializers run after all initializers have run. Because\ninstance initializers run after the app is fully set up. We have access\nto the store, container, and other items. However, these initializers run\nafter code has loaded and are not allowed to defer readiness.\n\nInstance initializer receives an object which has the following attributes:\n`name`, `before`, `after`, `initialize`. The only required attribute is\n`initialize`, all others are optional.\n\n* `name` allows you to specify under which name the instanceInitializer is\nregistered. This must be a unique name, as trying to register two\ninstanceInitializer with the same name will result in an error.\n\n```app/initializer/named-instance-initializer.js\nimport { debug } from '@ember/debug';\n\nexport function initialize() {\n  debug('Running named-instance-initializer!');\n}\n\nexport default {\n  name: 'named-instance-initializer',\n  initialize\n};\n```\n\n* `before` and `after` are used to ensure that this initializer is ran prior\nor after the one identified by the value. This value can be a single string\nor an array of strings, referencing the `name` of other initializers.\n\n* See Application.initializer for discussion on the usage of before\nand after.\n\nExample instanceInitializer to preload data into the store.\n\n```app/initializer/preload-data.js\n\nexport function initialize(application) {\n    var userConfig, userConfigEncoded, store;\n    // We have a HTML escaped JSON representation of the user's basic\n    // configuration generated server side and stored in the DOM of the main\n    // index.html file. This allows the app to have access to a set of data\n    // without making any additional remote calls. Good for basic data that is\n    // needed for immediate rendering of the page. Keep in mind, this data,\n    // like all local models and data can be manipulated by the user, so it\n    // should not be relied upon for security or authorization.\n\n    // Grab the encoded data from the meta tag\n    userConfigEncoded = document.querySelector('head meta[name=app-user-config]').attr('content');\n\n    // Unescape the text, then parse the resulting JSON into a real object\n    userConfig = JSON.parse(unescape(userConfigEncoded));\n\n    // Lookup the store\n    store = application.lookup('service:store');\n\n    // Push the encoded JSON into the store\n    store.pushPayload(userConfig);\n}\n\nexport default {\n  name: 'named-instance-initializer',\n  initialize\n};\n```",
       "itemtype": "method",
       "name": "instanceInitializer",
       "params": [
@@ -16490,7 +15696,7 @@
     },
     {
       "file": "packages/@ember/engine/index.js",
-      "line": 379,
+      "line": 378,
       "description": "This creates a registry with the default Ember naming conventions.\n\nIt also configures the registry:\n\n* registered views are created every time they are looked up (they are\n  not singletons)\n* registered templates are not factories; the registered value is\n  returned directly.\n* the router receives the application as its `namespace` property\n* all controllers receive the router as their `target` and `controllers`\n  properties\n* all controllers receive the application as their `namespace` property\n* the application view receives the application controller as its\n  `controller` property\n* the application view receives the application template as its\n  `defaultTemplate` property",
       "itemtype": "method",
       "name": "buildRegistry",
@@ -16513,7 +15719,7 @@
     },
     {
       "file": "packages/@ember/engine/index.js",
-      "line": 419,
+      "line": 418,
       "description": "Set this to provide an alternate class to `DefaultResolver`",
       "itemtype": "property",
       "name": "resolver",
@@ -16524,7 +15730,7 @@
     },
     {
       "file": "packages/@ember/engine/index.js",
-      "line": 428,
+      "line": 427,
       "description": "This function defines the default lookup rules for container lookups:\n\n* templates are looked up on `Ember.TEMPLATES`\n* other names are looked up on the application after classifying the name.\n  For example, `controller:post` looks up `App.PostController` by default.\n* if the default lookup fails, look for registered classes on the container\n\nThis allows the application to register default injections in the container\nthat could be overridden by the normal naming convention.",
       "access": "private",
       "tagname": "",
@@ -18908,7 +18114,7 @@
     },
     {
       "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/-internals/routing/lib/system/route.ts:2320"
+      "line": " packages/@ember/-internals/routing/lib/system/route.ts:2319"
     },
     {
       "message": "replacing incorrect tag: function with method",
@@ -18936,23 +18142,23 @@
     },
     {
       "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:149"
+      "line": " packages/@ember/-internals/glimmer/lib/components/abstract-input.ts:125"
     },
     {
       "message": "Missing item type\nThe HTML class attribute.",
-      "line": " packages/@ember/-internals/glimmer/lib/components/input.ts:174"
+      "line": " packages/@ember/-internals/glimmer/lib/components/input.ts:183"
     },
     {
       "message": "Missing item type\nThe HTML type attribute.",
-      "line": " packages/@ember/-internals/glimmer/lib/components/input.ts:185"
+      "line": " packages/@ember/-internals/glimmer/lib/components/input.ts:194"
     },
     {
       "message": "Missing item type\nThe default HTML id attribute. We don't really _need_ one, this is just\nadded for compatibility as it's hard to tell if people rely on it being\npresent, and it doens't really hurt.\n\nHowever, don't rely on this internally, like passing it to `getElementId`.\nThis can be (and often is) overriden by passing an `id` attribute on the\ninvocation, which shadows this default id via `...attributes`.",
-      "line": " packages/@ember/-internals/glimmer/lib/components/internal.ts:45"
+      "line": " packages/@ember/-internals/glimmer/lib/components/internal.ts:37"
     },
     {
       "message": "Missing item type\nThe default HTML class attribute. Similar to the above, we don't _need_\nthem, they are just added for compatibility as it's similarly hard to tell\nif people rely on it in their CSS etc, and it doens't really hurt.",
-      "line": " packages/@ember/-internals/glimmer/lib/components/internal.ts:58"
+      "line": " packages/@ember/-internals/glimmer/lib/components/internal.ts:50"
     },
     {
       "message": "Missing item type\nThis reference is used to get the `[]` tag of iterables, so we can trigger\nupdates to `{{each}}` when it changes. It is put into place by a template\ntransform at build time, similar to the (-each-in) helper",
@@ -19044,15 +18250,15 @@
     },
     {
       "message": "Missing item type\nFinds the name of the substate route if it exists for the given route. A\nsubstate route is of the form `route_state`, such as `foo_loading`.",
-      "line": " packages/@ember/-internals/routing/lib/system/router.ts:1584"
+      "line": " packages/@ember/-internals/routing/lib/system/router.ts:1547"
     },
     {
       "message": "Missing item type\nFinds the name of the state route if it exists for the given route. A state\nroute is of the form `route.state`, such as `foo.loading`. Properly Handles\n`application` named routes.",
-      "line": " packages/@ember/-internals/routing/lib/system/router.ts:1603"
+      "line": " packages/@ember/-internals/routing/lib/system/router.ts:1566"
     },
     {
       "message": "Missing item type\nDetermines whether or not a route has been defined by checking that the route\nis in the Router's map and the owner has a registration for that route.",
-      "line": " packages/@ember/-internals/routing/lib/system/router.ts:1623"
+      "line": " packages/@ember/-internals/routing/lib/system/router.ts:1586"
     },
     {
       "message": "Missing item type",
@@ -19191,12 +18397,12 @@
       "line": " packages/@ember/-internals/runtime/types/observable.d.ts:67"
     },
     {
-      "message": "Missing item type\nPreviously we used `Ember.$.uuid`, however `$.uuid` has been removed from\njQuery master. We'll just bootstrap our own uuid now.",
+      "message": "Missing item type",
       "line": " packages/@ember/-internals/utils/lib/guid.ts:8"
     },
     {
       "message": "Missing item type\nGenerates a universally unique identifier. This method\nis used internally by Ember for assisting with\nthe generation of GUID's and other unique identifiers.",
-      "line": " packages/@ember/-internals/utils/lib/guid.ts:17"
+      "line": " packages/@ember/-internals/utils/lib/guid.ts:14"
     },
     {
       "message": "Missing item type\nStrongly hint runtimes to intern the provided string.\n\nWhen do I need to use this function?\n\nFor the most part, never. Pre-mature optimization is bad, and often the\nruntime does exactly what you need it to, and more often the trade-off isn't\nworth it.\n\nWhy?\n\nRuntimes store strings in at least 2 different representations:\nRopes and Symbols (interned strings). The Rope provides a memory efficient\ndata-structure for strings created from concatenation or some other string\nmanipulation like splitting.\n\nUnfortunately checking equality of different ropes can be quite costly as\nruntimes must resort to clever string comparison algorithms. These\nalgorithms typically cost in proportion to the length of the string.\nLuckily, this is where the Symbols (interned strings) shine. As Symbols are\nunique by their string content, equality checks can be done by pointer\ncomparison.\n\nHow do I know if my string is a rope or symbol?\n\nTypically (warning general sweeping statement, but truthy in runtimes at\npresent) static strings created as part of the JS source are interned.\nStrings often used for comparisons can be interned at runtime if some\ncriteria are met.  One of these criteria can be the size of the entire rope.\nFor example, in chrome 38 a rope longer then 12 characters will not\nintern, nor will segments of that rope.\n\nSome numbers: http://jsperf.com/eval-vs-keys/8\n\nKnown Trick™",
@@ -19204,7 +18410,7 @@
     },
     {
       "message": "Missing item type\nUnfortunately, a lot of existing code assumes the booting process is\n\"synchronous\". Specifically, a lot of tests assumes the last call to\n`app.advanceReadiness()` or `app.reset()` will result in the app being\nfully-booted when the current runloop completes.\n\nWe would like new code (like the `visit` API) to stop making this assumption,\nso we created the asynchronous version above that returns a promise. But until\nwe have migrated all the code, we would have to expose this method for use\n*internally* in places where we need to boot an app \"synchronously\".",
-      "line": " packages/@ember/application/lib/application.js:665"
+      "line": " packages/@ember/application/lib/application.js:663"
     },
     {
       "message": "Missing item type\nOverrides the base `EngineInstance._bootSync` method with concerns relevant\nto booting application (instead of engine) instances.\n\nThis method should only contain synchronous boot concerns. Asynchronous\nboot concerns should eventually be moved to the `boot` method, which\nreturns a promise.\n\nUntil all boot code has been made asynchronous, we need to continue to\nexpose this method for use *internally* in places where we need to boot an\ninstance synchronously.",