bootPromiseprivate Defined in packages/ember-application/lib/system/application.js:541 Initialize the application and return a promise that resolves with the Ember.Application object when the boot process is complete. Run any application initializers and run the application load hook. These hooks may choose to defer readiness. For example, an authentication hook might want to defer readiness until the auth token has been retrieved. By default, this method is called automatically on "DOM rea

autobootBooleanprivate Defined in packages/ember-application/lib/system/application.js:281 Whether the application should automatically start routing and render templates to the rootElement on DOM ready. While default by true, other environments such as FastBoot or a testing harness can set this property to false and control the precise timing and behavior of the boot process. Default: true

advanceReadinesspublic Defined in packages/ember-application/lib/system/application.js:523 Call advanceReadiness after any asynchronous setup logic has completed. Each call to deferReadiness must be matched by a call to advanceReadiness or the application will never become ready and routing will not begin.

Ember.Application Class PUBLIC Extends: Ember.Engine Uses: RegistryProxyMixin Defined in: packages/ember-application/lib/system/application.js:45 Module: ember-application An instance of Ember.Application is the starting point for every Ember application. It helps to instantiate, initialize and coordinate the many objects that make up your app. Each Ember app has one and only one Ember.Application object. In fact, the very first thing you should do in your application is create the instanc

Adding Nested Routes Up to this point, we've generated four top level routes. An about route, that gives information on our application. A contact route, with information on how to contact the company. A rentals route, where we will allow users to browse rental properties. The index route, which we've set up to redirect to the rentals route. Our rentals route is going to serve multiple functions. From our acceptance tests, we've shown that we want our users to be able to browse and search r

Actions Your app will often need a way to let users interact with controls that change application state. For example, imagine that you have a template that shows a blog title, and supports expanding the post to show the body. If you add the {{action}} helper to any HTML DOM element, when a user clicks the element, the named event will be sent to the template's corresponding component or controller. app/templates/components/single-post.hbs <h3><button {{action "toggleBody"}}>{{tit

send (actionName, context) public Defined in packages/ember-runtime/lib/mixins/action_handler.js:145 Triggers a named action on the ActionHandler. Any parameters supplied after the actionName string will be passed as arguments to the action target function. If the ActionHandler has its target property set, actions may bubble to the target. Bubbling happens when an actionName can not be found in the ActionHandler's actions hash or if the action target function returns true. Example App.Welco

actionsObjectpublic Defined in packages/ember-runtime/lib/mixins/action_handler.js:24 The collection of functions, keyed by name, available on this ActionHandler as action targets. These functions will be invoked when a matching {{action}} is triggered from within a template and the application's current route is this route. Actions can also be invoked from other parts of your application via ActionHandler#send. The actions hash will inherit action handlers from the actions hash defined on

Ember.ActionHandler Class PRIVATE Defined in: packages/ember-runtime/lib/mixins/action_handler.js:10 Module: ember-runtime Ember.ActionHandler is available on some familiar classes including Ember.Route, Ember.View, Ember.Component, and Ember.Controller. (Internally the mixin is used by Ember.CoreView, Ember.ControllerMixin, and Ember.Route and available to the above classes through inheritance.)

Acceptance Tests To create an acceptance test, run ember generate acceptance-test <name>. For example: ember g acceptance-test login This generates this file: tests/acceptance/login-test.js import { test } from 'qunit'; import moduleForAcceptance from 'people/tests/helpers/module-for-acceptance'; moduleForAcceptance('Acceptance | login'); test('visiting /login', function(assert) { visit('/login'); andThen(function() { assert.equal(currentURL(), '/login'); }); }); moduleFo