ApplicationInstance.BootOptions#shouldRender

shouldRenderbooleanpublic Defined in packages/ember-application/lib/system/application-instance.js:376 Disable rendering completely. When this flag is set to true, it will disable the entire rendering pipeline. Essentially, this puts the app into "routing-only" mode. No templates will be rendered, and no Components will be created. Default: true

DS.Adapter#shouldBackgroundReloadRecord()

shouldBackgroundReloadRecord (store, snapshot) Boolean Defined in addon/adapter.js:580 Available since 1.13.0 This method is used by the store to determine if the store should reload a record after the store.findRecord method resolves a cached record. This method is only checked by the store when the store is returning a cached record. If this method returns true the store will re-fetch a record from the adapter. For example, if you do not want to fetch complex data over a mobile connection

DS.JSONAPISerializer#extractAttributes()

extractAttributes (modelClass, resourceHash) Object Inherited from DS.JSONSerializer but overwritten in addon/serializers/json-api.js:253 Parameters: modelClass DS.Model resourceHash Object Returns: Object

DS.Store#getReference()

getReference (type, id) RecordReference Defined in addon/-private/system/store.js:869 Available since 2.5.0 Get the reference for the specified record. Example var userRef = store.getReference('user', 1); // check if the user is loaded var isLoaded = userRef.value() !== null; // get the record of the reference (null if not yet available) var user = userRef.value(); // get the identifier of the reference if (userRef.remoteType() === "id") { var id = userRef.id(); } // load user (via stor

DS.Adapter#queryRecord()

queryRecord (store, type, query) Promise Defined in addon/adapter.js:184 The queryRecord() method is invoked when the store is asked for a single record through a query object. In response to queryRecord() being called, you should always fetch fresh data. Once found, you can asynchronously call the store's push() method to push the record into the store. Here is an example queryRecord implementation: Example app/adapters/application.js import DS from 'ember-data'; import Ember from 'ember';

DS.JSONSerializer#normalizeQueryResponse()

normalizeQueryResponse (store, primaryModelClass, payload, id, requestType) Object Defined in addon/serializers/json.js:346 Available since 1.13.0 Parameters: store DS.Store primaryModelClass DS.Model payload Object id String|Number requestType String Returns: Object JSON-API Document

Ember.removeListener()

removeListener (obj, eventName, target, method) public Defined in packages/ember-metal/lib/events.js:112 Remove an event listener Arguments should match those passed to Ember.addListener. Parameters: obj eventName String target Object|Function A target object or a function method Function|String A function or the name of a function to be called on `target`

DS.Store#recordWasInvalid()

recordWasInvalid (internalModel, errors) private Defined in addon/-private/system/store.js:1771 This method is called once the promise returned by an adapter's createRecord, updateRecord or deleteRecord is rejected with a DS.InvalidError. Parameters: internalModel InternalModel errors Object

HistoryLocation#willDestroy()

willDestroyprivate Inherited from Ember.CoreObject but overwritten in packages/ember-routing/lib/location/history_location.js:221 Cleans up the HistoryLocation event listener.

DS.RESTSerializer

DS.RESTSerializer Class Extends: DS.JSONSerializer Defined in: addon/serializers/rest.js:16 Module: ember-data Normally, applications will use the RESTSerializer by implementing the normalize method. This allows you to do whatever kind of munging you need, and is especially useful if your server is inconsistent and you need to do munging differently for many different kinds of responses. See the normalize documentation for more information. Across the Board Normalization There are also a n