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.)

urlStringprivate Defined in packages/ember-routing/lib/system/router.js:158 Represents the current URL. Returns: String The current URL.

Customizing a Component's Element By default, each component is backed by a <div> element. If you were to look at a rendered component in your developer tools, you would see a DOM representation that looked something like: <div id="ember180" class="ember-view"> <h1>My Component</h1> </div> You can customize what type of element Ember generates for your component, including its attributes and class names, by creating a subclass of Ember.Component in your JavaSc

Object Inspector The Inspector includes a panel that allows you to view and interact with your Ember objects. To open it, click on any Ember object. You can then view the object's properties. Viewing Objects Here's what you see when you click on an object: The Inspector displays the parent objects and mixins that are composed into the chosen object, including the inherited properties. Each property value in this view is bound to your application, so if the value of a property updates in your

DS.SnapshotRecordArray Class PRIVATE Defined in: addon/-private/system/snapshot-record-array.js:5 Module: ember-data

DS.Store Class Extends: Ember.Service Defined in: addon/-private/system/store.js:140 Module: ember-data The store contains all of the data for records loaded from the server. It is also responsible for creating instances of DS.Model that wrap the individual data for a record, so that they can be bound to in your Handlebars templates. Define your application's store like this: app/services/store.js import DS from 'ember-data'; export default DS.Store.extend({ }); Most Ember.js application

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

data{Object}private Defined in addon/-private/system/model/model.js:947

elementDOMElementpublic Defined in packages/ember-views/lib/mixins/view_support.js:87 Returns the current DOM element for the view.

debug (message) public Defined in packages/ember-debug/lib/index.js:60 Display a debug notice. In a production build, this method is defined as an empty function (NOP). Uses of this method in Ember itself are stripped from the ember.prod.js build. Ember.debug('I\'m a debug notice!'); Parameters: message String A debug message to display.