Transition#method()

method (method) Transitionpublic Defined in bower_components/router.js/lib/router/transition.js:223 Sets the URL-changing method to be employed at the end of a successful transition. By default, a new Transition will just use updateURL, but passing 'replace' to this method will cause the URL to update using 'replaceWith' instead. Omitting a parameter will disable the URL change, allowing for transitions that don't update the URL at completion (this is also used for handleURL, since the URL

Transition#finally()

finally (callback, label) Promisepublic Defined in bower_components/router.js/lib/router/transition.js:172 Forwards to the internal promise property which you can use in situations where you want to pass around a thennable, but not the Transition itself. Parameters: callback Function label String optional string for labeling the promise. Useful for tooling. Returns: Promise

Transition#data

data{Object}public Defined in bower_components/router.js/lib/router/transition.js:122 Custom state can be stored on a Transition's data object. This can be useful for decorating a Transition within an earlier hook and shared with a later hook. Properties set on data will be copied to new transitions generated by calling retry on this transition.

Transition#abort()

abortTransitionpublic Defined in bower_components/router.js/lib/router/transition.js:189 Aborts the Transition. Note you can also implicitly abort a transition by initiating another transition while a previous one is underway. Returns: Transition this transition

Transition#catch()

catch (onRejection, label) Promisepublic Defined in bower_components/router.js/lib/router/transition.js:155 Forwards to the internal promise property which you can use in situations where you want to pass around a thennable, but not the Transition itself. Parameters: onRejection Function label String optional string for labeling the promise. Useful for tooling. Returns: Promise

Transition

Transition Class PRIVATE Defined in: bower_components/router.js/lib/router/transition.js:4 Module: ember A Transition is a thennable (a promise-like object) that represents an attempt to transition to another route. It can be aborted, either explicitly via abort or by attempting another transition while a previous one is still underway. An aborted transition can also be retry()d later.

The Component Lifecycle

The Component Lifecycle Part of what makes components so useful is that they let you take complete control of a section of the DOM. This allows for direct DOM manipulation, listening and responding to browser events, and using 3rd party JavaScript libraries in your Ember app. As components are rendered, re-rendered and finally removed, Ember provides lifecycle hooks that allow you to run code at specific times in a component's life. To get the most use out of a component, it is important to u

The Run Loop

The Run Loop Ember's internals and most of the code you will write in your applications takes place in a run loop. The run loop is used to batch, and order (or reorder) work in a way that is most effective and efficient. It does so by scheduling work on specific queues. These queues have a priority, and are processed to completion in priority order. For basic Ember app development scenarios, you don't need to understand the run loop or use it directly. All common paths are paved nicely for yo

The Model Hook

The Model Hook Now, let's add a list of available rentals to the index template. We know that rentals will not be static, since eventually users will be able to add, update, and delete them. For this reason, we'll need a rentals model to save information about the rentals. To keep things simple at first, we'll use a hard-coded array of JavaScript objects. Later, we'll switch to using Ember Data, a library for robustly managing data in our app. Here's what our homepage will look like when we'r

The View Tree

The View Tree You can use the View Tree to inspect your application's current state. The View Tree shows you the currently rendered templates, models, controllers, and components, in a tree format. Click on the View Tree menu on the left to see these. Use the tips described in Object Inspector to inspect models and controllers. See below for templates and components. Inspecting Templates To see how a template was rendered by Ember, click on the template in the View Tree. If you're using Chro