reject (reason, label) Promisestatic Inherited from RSVP but overwritten in bower_components/rsvp/lib/rsvp/reject.js:3 This is a convenient alias for RSVP.Promise.reject. Parameters: reason * value that the returned promise will be rejected with. label String optional string for identifying the returned promise. Useful for tooling. Returns: Promise a promise rejected with the given `reason`.

Library Info To see a list of libraries used in your application, click on the Info menu. This view displays the libraries used, along with their version. Registering a Library If you would like to add your own application or library to the list, you can register it using: Ember.libraries.register(libraryName, libraryVersion); Ember Cli If you're using the ember-cli-app-version addon, your application's name and version will be added to the list automatically.

eachComputedProperty (callback, binding) privatestatic Defined in packages/ember-runtime/lib/system/core_object.js:853 Iterate over each computed property for the class, passing its name and any associated metadata (see metaForProperty) to the callback. Parameters: callback Function binding Object

then (onFulfilled, onRejected, label) Promisepublic Defined in bower_components/router.js/lib/router/transition.js:135 A standard promise hook that resolves if the transition succeeds and rejects if it fails/redirects/aborts. 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: onFulfilled Function onRejected Function label String optional string for labeling the promise. Us

findMany (store, type, ids, snapshots) Promise Defined in addon/adapter.js:423 The store will call findMany instead of multiple findRecord requests to find multiple records at once if coalesceFindRequests is true. app/adapters/application.js import DS from 'ember-data'; export default DS.Adapter.extend({ findMany(store, type, ids, snapshots) { return new Ember.RSVP.Promise(function(resolve, reject) { Ember.$.ajax({ type: 'GET', url: `/${type.modelName}/`,

without (value) Ember.Enumerablepublic Defined in packages/ember-runtime/lib/mixins/enumerable.js:790 Returns a new enumerable that excludes the passed value. The default implementation returns an array regardless of the receiver type. If the receiver does not contain the value it returns the original enumerable. let arr = ['a', 'b', 'a', 'c']; arr.without('a'); // ['b', 'c'] Parameters: value Object Returns: Ember.Enumerable

Handling Metadata Along with the records returned from your store, you'll likely need to handle some kind of metadata. Metadata is data that goes along with a specific model or type instead of a record. Pagination is a common example of using metadata. Imagine a blog with far more posts than you can display at once. You might query it like so: let result = this.get('store').query('post', { limit: 10, offset: 0 }); To get different pages of data, you'd simply change your offset in increme

ember-extension-support Module Parent: ember The ContainerDebugAdapter helps the container and resolver interface with tools that debug Ember such as the Ember Extension for Chrome and Firefox. This class can be extended by a custom resolver implementer to override some of the methods with library-specific code. The methods likely to be overridden are: canCatalogEntriesByType catalogEntriesByType The adapter will need to be registered in the application's container as container-debug-adapter:

ember-views Module Parent: ember The internal class used to create text inputs when the {{input}} helper is used with type of checkbox. See Ember.Templates.helpers.input for usage details. Direct manipulation of checked The checked attribute of an Ember.Checkbox object should always be set through the Ember object or by interacting with its rendered element representation via the mouse, keyboard, or touch. Updating the value of the checkbox via jQuery will result in the checked value of the ob

Using Ember Data Currently, our app is using hard-coded data for rentals in the rentals route handler to set the model. As our application grows, we will want to be able to create new rentals, make updates to them, delete them, and save these changes to a backend server. Ember integrates with a data management library called Ember Data to help solve this problem. Let's generate our first Ember Data model called rental: ember g model rental This results in the creation of a model file and a t