Ext.data.NodeStore alias: store.node private

asynchronousLoad : Boolean

This defaults to true when this store's cfg-proxy is asynchronous, such as an Ext.data.proxy.Ajax.

When the proxy is synchronous, such as a Ext.data.proxy.Memory memory proxy, this defaults to false.

NOTE: This does not cause synchronous Ajax requests if configured false when an Ajax proxy is used. It causes immediate issuing of an Ajax request when method-load is called rather than issuing the request at the end of the current event handler run.

What this means is that when using an Ajax proxy, calls to method-load do not fire the request to the remote resource immediately, but schedule a request to be made. This is so that multiple requests are not fired when mutating a store's remote filters and sorters (as happens during state restoration). The request is made only once after all relevant store state is fully set.

Defaults to:

undefined

Available since: 6.0.1

autoDestroy : Boolean

When a Store is used by only one Ext.view.View, and should only exist for the lifetime of that view, then configure the autoDestroy flag as true. This causes the destruction of the view to trigger the destruction of its Store.

Defaults to:

undefined

autoLoad : Boolean / Object

If data is not specified, and if autoLoad is true or an Object, this store's load method is automatically called after creation. If the value of autoLoad is an Object, this Object will be passed to the store's load method.

It's important to note that Ext.data.TreeStore will load regardless of autoLoad's value if expand is set to true on the root node.

Defaults to:

undefined

Available since: 2.3.0

autoSync : Boolean

True to automatically sync the Store with its Proxy after every edit to one of its Records. Defaults to false.

Defaults to:

false

batchUpdateMode : String

Sets the updating behavior based on batch synchronization. 'operation' (the default) will update the Store's internal representation of the data after each operation of the batch has completed, 'complete' will wait until the entire batch has been completed before updating the Store's data. 'complete' is a good choice for local storage proxies, 'operation' is better for remote proxies, where there is a comparatively high latency.

Defaults to:

'operation'

clearOnPageLoad : Boolean

True to empty the store when loading another page via loadPage, nextPage or previousPage. Setting to false keeps existing records, allowing large data sets to be loaded one page at a time but rendered all together.

Defaults to:

true

clearRemovedOnLoad : Boolean

true to clear anything in the removed record collection when the store loads.

Defaults to:

true

data : Object[] / Ext.data.Model[]

Array of Model instances or data objects to load locally. See "Inline data" above for details.

Defaults to:

undefined

fields : Object[] / String[]

An Array of Ext.data.field.Field config objects, simply the field name, or a mix of config objects and strings. If just a name is given, the field type defaults to auto.

In a Ext.data.field.Field config object you may pass the alias of the Ext.data.field.* type using the type config option.

// two fields are set:
// - an 'auto' field with a name of 'firstName'
// - and an Ext.data.field.Integer field with a name of 'age'
fields: ['firstName', {
    type: 'int',
    name: 'age'
}]

Fields will automatically be created at read time for any for any keys in the data passed to the Model's proxy's Ext.data.reader.Reader whose name is not explicitly configured in the fields config.

Extending a Model class will inherit all the fields from the superclass / ancestor classes. Note: In general, this configuration option should only be used for simple stores like a two-field store of Ext.form.field.ComboBox. For anything more complicated, such as specifying a particular id property or associations, a Ext.data.Model should be defined and specified for the model config.

Defaults to:

null

Available since: 2.3.0

filters : Object[] / Function[] / Ext.util.Collection

Array of Ext.util.Filter for this store. Can also be an array of functions which will be used as the filterFn config for filters:

filters: [
    function(item) {
        return item.weight > 0;
    }
]

Individual filters can be specified as an Ext.util.Filter instance, a config object for Ext.util.Filter or simply a function that will be wrapped in a instance with its filterFn set.

If a Collection of filters is passed, its items (filters) will be added. Any subsequent modification to the collection will have no affect.

For fine grain control of the filters collection, call getFilters to return the Ext.util.Collection instance that holds this store's filters.

 var filters = store.getFilters(); // an Ext.util.FilterCollection

 function legalAge (item) {
     return item.age >= 21;
 }

 filters.add(legalAge);

 //...

 filters.remove(legalAge);

Any changes to the filters collection will cause this store to adjust its items accordingly.

Defaults to:

null

groupDir : String

The direction in which sorting should be applied when grouping. Supported values are "ASC" and "DESC".

Defaults to:

'ASC'

grouper : Object / Ext.util.Grouper

The grouper by which to group the data store. May also be specified by the groupField config, however they should not be used together.

Defaults to:

null

groupField : String

The field by which to group data in the store. Internally, grouping is very similar to sorting - the groupField and groupDir are injected as the first sorter (see method-sort). Stores support a single level of grouping, and groups can be fetched via the getGroups method.

Defaults to:

undefined

listeners : Object

A config object containing one or more event handlers to be added to this object during initialization. This should be a valid listeners config object as specified in the addListener example for attaching multiple handlers at once.

DOM events from Ext JS Ext.Component

While some Ext JS Component classes export selected DOM events (e.g. "click", "mouseover" etc), this is usually only done when extra value can be added. For example the Ext.view.View's itemclick event passing the node clicked on. To access DOM events directly from a child element of a Component, we need to specify the element option to identify the Component property to add a DOM listener to:

new Ext.panel.Panel({
    width: 400,
    height: 200,
    dockedItems: [{
        xtype: 'toolbar'
    }],
    listeners: {
        click: {
            element: 'el', //bind to the underlying el property on the panel
            fn: function(){ console.log('click el'); }
        },
        dblclick: {
            element: 'body', //bind to the underlying body property on the panel
            fn: function(){ console.log('dblclick body'); }
        }
    }
});

model : String / Ext.data.Model

Name of the Ext.data.Model associated with this store. See Ext.data.Model#entityName.

May also be the actual Model subclass.

This config is required for the store to be able to read data unless you have defined the fields config which will create an anonymous Ext.data.Model.

Defaults to:

undefined

pageSize : Number

The number of records considered to form a 'page'. This is used to power the built-in paging using the nextPage and previousPage functions when the grid is paged using a Ext.toolbar.Paging Defaults to 25.

To disable paging, set the pageSize to 0.

Defaults to:

25

proxy : String / Ext.data.proxy.Proxy / Object

The Proxy to use for this Store. This can be either a string, a config object or a Proxy instance - see setProxy for details.

Defaults to:

undefined

Available since: 1.1.0

reloadOnClearSorters : Boolean

Set this to true to trigger a reload when the last sorter is removed (only applicable when remoteSort is true).

By default, the store reloads itself when a sorter is added or removed.

When the last sorter is removed, however, the assumption is that the data does not need to become "unsorted", and so no reload is triggered.

If the server has a default order to which it reverts in the absence of any sorters, then it is useful to set this config to true.

Defaults to:

false

Available since: 6.5.1

remoteFilter : Boolean

true to defer any filtering operation to the server. If false, filtering is done locally on the client.

Defaults to:

false

remoteSort : Boolean

true if the sorting should be performed on the server side, false if it is local only.

Defaults to:

false

session : Ext.data.Session

The session for this store. By specifying a session, it ensures any records that are added to this store are also included in the session. This store does not become a member of the session itself.

Defaults to:

null

Available since: 5.0.0

sorters : Ext.util.Sorter[] / Object[]

The initial set of Ext.util.Sorter

Individual sorters can be specified as an Ext.util.Sorter instance, a config object for Ext.util.Sorter or simply the name of a property by which to sort.

An alternative way to extend the sorters is to call the sort method and pass a property or sorter config to add to the sorters.

For fine grain control of the sorters collection, call getSorters to return the Ext.util.Collection instance that holds this collection's sorters.

 var sorters = store.getSorters(); // an Ext.util.SorterCollection

 sorters.add('name');

 //...

 sorters.remove('name');

Any changes to the sorters collection will cause this store to adjust its items accordingly.

Defaults to:

null

sortOnLoad : Boolean

If true, any sorters attached to this Store will be run after loading data, before the datachanged event is fired. Defaults to true, ignored if remoteSort is true

Defaults to:

true

statefulFilters : Boolean

Configure as true to have the filters saved when a client Ext.grid.Panel saves its state.

Defaults to:

false

storeId : String

Unique identifier for this store. If present, this Store will be registered with the Ext.data.StoreManager, making it easy to reuse elsewhere.

Note that when a store is instantiated by a Controller, the storeId will default to the name of the store if not specified in the class.

Defaults to:

null

trackRemoved : Boolean

This config controls whether removed records are remembered by this store for later saving to the server.

Defaults to:

true

currentPage : Number

The page that the Store has most recently loaded (see loadPage)

Defaults to:

1

destroyed : Boolean

This property is set to true after the destroy method is called.

Defaults to:

false

doDestroy

Perform the Store destroying sequence. Override this method to add destruction behaviors to your custom Stores.

Defaults to:

Ext.emptyFn

factoryConfig : Object

If this property is specified by the target class of this mixin its properties are used to configure the created Ext.Factory.

hasListeners : Object

readonly ro

This object holds a key for any event that has a listener. The listener may be set directly on the instance, or on its class or a super class (via observe) or on the Ext.app.EventBus. The values of this object are truthy (a non-zero number) and falsy (0 or undefined). They do not represent an exact count of listeners. The value for an event is truthy if the event must be fired and is falsy if there is no need to fire the event.

The intended use of this property is to avoid the expense of fireEvent calls when there are no listeners. This can be particularly helpful when one would otherwise have to call fireEvent hundreds or thousands of times. It is used like this:

 if (this.hasListeners.foo) {
     this.fireEvent('foo', this, arg1);
 }

isObservable : Boolean

true in this class to identify an object as an instantiated Observable, or subclass thereof.

Defaults to:

true

isStore : Boolean

true in this class to identify an object as an instantiated Store, or subclass thereof.

Defaults to:

true

lastOptions : Object

Property to hold the last options from a method-load method call. This object is used for the method-reload to reuse the same options. Please see method-reload for a simple example on how to use the lastOptions property.

loadCount : Number

readonly ro

The number of times records have been loaded into the store. This includes loads via loadData & loadRecords.

Defaults to:

0

updating : Number

readonly ro

A counter that is increased by beginUpdate and decreased by endUpdate. When this transitions from 0 to 1 the beginupdate event is fired. When it transitions back from 1 to 0 the endupdate event is fired.

Defaults to:

0

Available since: 5.0.0

add ( record ) : Ext.data.Model[]

Adds Model instance to the Store. This method accepts either:

• An array of Model instances or Model configuration objects.
• Any number of Model instance or Model configuration object arguments.

The new Model instances will be added at the end of the existing collection.

Sample usage:

myStore.add({some: 'data'}, {some: 'other data'});

Note that if this Store is sorted, the new Model instances will be inserted at the correct point in the Store to maintain the sort order.

Parameters

Returns

addAfterListener

Alias for onAfter.

addBeforeListener

Alias for onBefore.

addFilter ( filters, [suppressEvent] )

Adds a new Filter to this Store's filter set and by default, applies the updated filter set to the Store's unfiltered dataset.

Parameters

addListener ( eventName, [fn], [scope], [options], [order] ) : Object

chainable ch

The on method is shorthand for addListener.

Appends an event handler to this object. For example:

myGridPanel.on("itemclick", this.onItemClick, this);

The method also allows for a single argument to be passed which is a config object containing properties which specify multiple events. For example:

myGridPanel.on({
    cellclick: this.onCellClick,
    select: this.onSelect,
    viewready: this.onViewReady,
    scope: this // Important. Ensure "this" is correct during handler execution
});

One can also specify options for each event handler separately:

myGridPanel.on({
    cellclick: {fn: this.onCellClick, scope: this, single: true},
    viewready: {fn: panel.onViewReady, scope: panel}
});

Names of methods in a specified scope may also be used:

myGridPanel.on({
    cellclick: {fn: 'onCellClick', scope: this, single: true},
    viewready: {fn: 'onViewReady', scope: panel}
});

Parameters

  var panel = new Ext.panel.Panel({
      title: 'The title',
      listeners: {
          click: this.handlePanelClick,
          element: 'body'
      }
  });

 panel.body.un(...)

 handler('foo', 42, <actual event arguments>...);

false

'current'

Returns

this.btnListeners =  = myButton.on({
    destroyable: true
    mouseover:   function() { console.log('mouseover'); },
    mouseout:    function() { console.log('mouseout'); },
    click:       function() { console.log('click'); }
});

Ext.destroy(this.btnListeners);

this.btnListeners.destroy();

addManagedListener ( item, ename, [fn], [scope], [options] ) : Object

The addManagedListener method is used when some object (call it "A") is listening to an event on another observable object ("B") and you want to remove that listener from "B" when "A" is destroyed. This is not an issue when "B" is destroyed because all of its listeners will be removed at that time.

Example:

Ext.define('Foo', {
    extend: 'Ext.Component',

    initComponent: function () {
        this.addManagedListener(MyApp.SomeSharedMenu, 'show', this.doSomething);
        this.callParent();
    }
});

As you can see, when an instance of Foo is destroyed, it ensures that the 'show' listener on the menu (MyApp.SomeGlobalSharedMenu) is also removed.

As of version 5.1 it is no longer necessary to use this method in most cases because listeners are automatically managed if the scope object provided to addListener is an Observable instance. However, if the observable instance and scope are not the same object you still need to use mon or addManagedListener if you want the listener to be managed.

Parameters

Returns

this.btnListeners = myButton.mon({
    destroyable: true
    mouseover:   function() { console.log('mouseover'); },
    mouseout:    function() { console.log('mouseout'); },
    click:       function() { console.log('click'); }
});

Ext.destroy(this.btnListeners);

this.btnListeners.destroy();

addSorted ( record )

(Local sort only) Inserts the passed Record into the Store at the index where it should go based on the current sort information.

Parameters

aggregate ( fn, [scope], [grouped], field ) : Object

Runs the aggregate function for all the records in the store.

When store is filtered, only items within the filter are aggregated.

Parameters

Returns

average ( field, [grouped] ) : Object

Gets the average value in the store.

When store is filtered, only items within the filter are aggregated.

Parameters

Returns

beginUpdate

This method may be called to indicate the start of multiple changes to the store.

Automatic synchronization as configured by the autoSync flag is deferred until the endUpdate method is called, so multiple mutations can be coalesced into one synchronization operation.

Internally this method increments a counter that is decremented by endUpdate. It is important, therefore, that if you call beginUpdate directly you match that call with a call to endUpdate or you will prevent the collection from updating properly.

For example:

 var store = Ext.StoreManager.lookup({
     //...
     autoSync: true
 });

 store.beginUpdate();

 record.set('fieldName', 'newValue');

 store.add(item);
 // ...

 store.insert(index, otherItem);
 //...

 // Interested parties will listen for the endupdate event
 store.endUpdate();

Available since: 5.0.0

clearFilter ( [suppressEvent] )

Reverts to a view of the Record cache with no filtering applied.

Parameters

clearGrouping

Clear the store grouping

clearListeners

Removes all listeners for this object including the managed listeners

clearManagedListeners

Removes all managed listeners for this object.

collect ( property, [includeOptions], [filtered] ) : Object[]

Collects unique values for a particular dataIndex from this store.

Note that the filtered option can also be passed as a separate parameter for compatibility with previous versions.

var store = Ext.create('Ext.data.Store', {
    fields: ['name'],
    data: [{
        name: 'Larry'
    }, {
        name: 'Darryl'
    }, {
        name: 'Darryl'
    }]
});

store.collect('name');
// returns ["Larry", "Darryl"]

Parameters

Returns

commitChanges

Commits all Records with outstanding changes. To handle updates for changes, subscribe to the Store's update event, and perform updating when the third parameter is Ext.data.Record.COMMIT.

constructor ( [config] )

Creates the store.

Parameters

contains ( record ) : Boolean

Checks if a record is in the current active data set.

Parameters

Returns

count ( [grouped] ) : Number

Gets the count of items in the store.

When store is filtered, only items within the filter are counted.

Parameters

Returns

createActiveRange ( [config] ) : Ext.data.Range

Create a Range instance to access records by their index.

Available since: 6.5.0

Parameters

Returns

destroy

This method is called to cleanup an object and its resources. After calling this method, the object should not be used any further in any way, including access to its methods and properties.

To prevent potential memory leaks, all object references will be nulled at the end of destruction sequence, unless clearPropertiesOnDestroy is set to false.

destroyMembers ( args )

Destroys member properties by name.

If a property name is the name of a config, the getter is not invoked, so if the config has not been initialized, nothing will be done.

The property will be destroyed, and the corrected name (if the property is a config and config names are prefixed) will set to null in this object's dictionary.

Parameters

each ( fn, [scope], [includeOptions] )

Calls the specified function for each Ext.data.Model in the store.

When store is filtered, only loops over the filtered records.

Parameters

enableBubble ( eventNames )

Enables events fired by this Observable to bubble up an owner hierarchy by calling this.getBubbleTarget() if present. There is no implementation in the Observable base class.

This is commonly used by Ext.Components to bubble events to owner Containers. See Ext.Component#getBubbleTarget. The default implementation in Ext.Component returns the Component's immediate owner. But if a known target is required, this can be overridden to access the required target more quickly.

Example:

Ext.define('Ext.overrides.form.field.Base', {
    override: 'Ext.form.field.Base',

    //  Add functionality to Field's initComponent to enable
    // the change event to bubble
    initComponent: function () {
        this.callParent();
        this.enableBubble('change');
    }
});

var myForm = Ext.create('Ext.form.Panel', {
    title: 'User Details',
    items: [{
        ...
    }],
    listeners: {
        change: function() {
            // Title goes red if form has been modified.
            myForm.header.setStyle('color', 'red');
        }
    }
});

Parameters

endUpdate

This method is called after modifications are complete on a store. For details see beginUpdate.

Available since: 5.0.0

filter ( [filters], [value] )

Filters the data in the Store by one or more fields. Example usage:

//filter with a single field
myStore.filter('firstName', 'Don');

//filtering with multiple filters
myStore.filter([
    {
        property : 'firstName',
        value    : 'Don'
    },
    {
        property : 'lastName',
        value    : 'Griffin'
    }
]);

Internally, Store converts the passed arguments into an array of Ext.util.Filter instances, and delegates the actual filtering to its internal Ext.util.Collection or the remote server.

Parameters

filterBy ( fn, [scope] )

Filters by a function. The specified function will be called for each Record in this Store. If the function returns true the Record is included, otherwise it is filtered out.

When store is filtered, most of the methods for accessing store data will be working only within the set of filtered records. The notable exception is getById.

Parameters

find ( property, value, [startIndex], [anyMatch], [caseSensitive], [exactMatch] ) : Number

Finds the index of the first matching Record in this store by a specific field value.

When store is filtered, finds records only within filter.

IMPORTANT

If this store is Ext.data.BufferedStore, this can ONLY find records which happen to be cached in the page cache. This will be parts of the dataset around the currently visible zone, or recently visited zones if the pages have not yet been purged from the cache.

Parameters

Returns

findBy ( fn, [scope], [start] ) : Number

Find the index of the first matching Record in this Store by a function. If the function returns true it is considered a match.

When store is filtered, finds records only within filter.

IMPORTANT

If this store is Ext.data.BufferedStore, this can ONLY find records which happen to be cached in the page cache. This will be parts of the dataset around the currently visible zone, or recently visited zones if the pages have not yet been purged from the cache.

Parameters

Returns

findExact ( fieldName, value, [startIndex] ) : Number

Finds the index of the first matching Record in this store by a specific field value.

When store is filtered, finds records only within filter.

IMPORTANT

If this store is Ext.data.BufferedStore, this can ONLY find records which happen to be cached in the page cache. This will be parts of the dataset around the currently visible zone, or recently visited zones if the pages have not yet been purged from the cache.

Parameters

Returns

findRecord ( fieldName, value, [startIndex], [anyMatch], [caseSensitive], [exactMatch] ) : Ext.data.Model

Finds the first matching Record in this store by a specific field value.

When store is filtered, finds records only within filter.

IMPORTANT

If this store is Ext.data.BufferedStore, this can ONLY find records which happen to be cached in the page cache. This will be parts of the dataset around the currently visible zone, or recently visited zones if the pages have not yet been purged from the cache.

Parameters

Returns

fireEvent ( eventName, args ) : Boolean

Fires the specified event with the passed parameters (minus the event name, plus the options object passed to addListener).

An event may be set to bubble up an Observable parent hierarchy (See Ext.Component#getBubbleTarget) by calling enableBubble.

Parameters

Returns

fireEventArgs ( eventName, args ) : Boolean

Fires the specified event with the passed parameter list.

An event may be set to bubble up an Observable parent hierarchy (See Ext.Component#getBubbleTarget) by calling enableBubble.

Parameters

Returns

fireEventedAction ( eventName, args, fn, [scope], [fnArgs] ) : Boolean

Fires the specified event with the passed parameters and executes a function (action). Evented Actions will automatically dispatch a 'before' event passing. This event will be given a special controller that allows for pausing/resuming of the event flow.

By pausing the controller the updater and events will not run until resumed. Pausing, however, will not stop the processing of any other before events.

Parameters

Returns

first ( [grouped] ) : Ext.data.Model/undefined

Convenience function for getting the first model instance in the store.

When store is filtered, will return first item within the filter.

Parameters

Returns

flushLoad

Called when the event handler which called the method-load method exits.

getAt ( index ) : Ext.data.Model

Get the Record at the specified index.

The index is effected by filtering.

Parameters

Returns

getById ( id ) : Ext.data.Model

Get the Record with the specified id.

This method is not affected by filtering, lookup will be performed from all records inside the store, filtered or not.

Parameters

Returns

getByInternalId ( internalId ) : Ext.data.Model

Get the Record with the specified internalId.

This method is not affected by filtering, lookup will be performed from all records inside the store, filtered or not.

Parameters

Returns

getConfig ( [name], [peek], [ifInitialized] ) : Object

Returns a specified config property value. If the name parameter is not passed, all current configuration options will be returned as key value pairs.

Parameters

Returns

getCount Number

Gets the number of records in store.

If using paging, this may not be the total size of the dataset. If the data object used by the Reader contains the dataset size, then the Ext.data.ProxyStore#getTotalCount function returns the dataset size. Note: see the Important note in Ext.data.ProxyStore#method-load.

When store is filtered, it's the number of records matching the filter.

Returns

getData

getFilters

getGroups Ext.util.Collection

Returns a collection of readonly sub-collections of your store's records with grouping applied. These sub-collections are maintained internally by the collection.

See groupField, groupDir. Example for a store containing records with a color field:

var myStore = Ext.create('Ext.data.Store', {
    groupField: 'color',
    groupDir  : 'DESC'
});

myStore.getGroups();

The above should result in the following format:

[
    {
        name: 'yellow',
        children: [
            // all records where the color field is 'yellow'
        ]
    },
    {
        name: 'red',
        children: [
            // all records where the color field is 'red'
        ]
    }
]

Group contents are affected by filtering.

Returns

getId String

Retrieves the id. This method Will auto-generate an id if one has not already been configured.

Returns

getInitialConfig ( [name] ) : Object/Mixed

Returns the initial configuration passed to the constructor when instantiating this class.

Given this example Ext.button.Button definition and instance:

Ext.define('MyApp.view.Button', {
    extend: 'Ext.button.Button',
    xtype: 'mybutton',

    scale: 'large',
    enableToggle: true
});

var btn = Ext.create({
    xtype: 'mybutton',
    renderTo: Ext.getBody(),
    text: 'Test Button'
});

Calling btn.getInitialConfig() would return an object including the config options passed to the create method:

xtype: 'mybutton',
renderTo: // The document body itself
text: 'Test Button'

Calling btn.getInitialConfig('text')returns 'Test Button'.

Parameters

Returns

getModifiedRecords Ext.data.Model[]

Gets all Ext.data.Model added or updated since the last commit. Note that the order of records returned is not deterministic and does not indicate the order in which records were modified. Note also that removed records are not included (use getRemovedRecords for that).

Returns

getNewRecords Ext.data.Model[]

Returns all phantom records in this store.

Returns

getRange ( start, end ) : Ext.data.Model[]

Gathers a range of Records between specified indices.

This method is affected by filtering.

Parameters

Returns

getRemovedRecords Ext.data.Model[]

Returns any records that have been removed from the store but not yet destroyed on the proxy.

Returns

getSorters

getSummaryRecord Ext.data.Model

Get the summary record for this store. See Ext.data.Model#summary.

Available since: 6.5.0

Returns

getTotalCount Number

Returns the total number of Ext.data.Model instances that the Ext.data.proxy.Proxy indicates exist. This will usually differ from getCount when using paging - getCount returns the number of records loaded into the Store at the moment, getTotalCount returns the number of records that could be loaded into the Store if the Store contained all data

Returns

getUpdatedRecords Ext.data.Model[]

Returns all valid, non-phantom Model instances that have been updated in the Store but not yet synchronized with the Proxy.

Returns

group ( grouper, [direction] )

Groups data inside the store.

Parameters

hasListener ( eventName ) : Boolean

Checks to see if this object has any listeners for a specified event, or whether the event bubbles. The answer indicates whether the event needs firing or not.

Parameters

Returns

indexOf ( record ) : Number

Get the index of the record within the store.

When store is filtered, records outside of filter will not be found.

Parameters

Returns

indexOfId ( id ) : Number

Get the index within the store of the Record with the passed id.

Like #indexOf, this method is affected by filtering.

Parameters

Returns

insert ( index, records ) : Ext.data.Model[]

Inserts Model instances into the Store at the given index and fires the add event. See also method-add.

Parameters

Returns

isFiltered Boolean

Tests whether the store currently has any active filters.

Returns

isGrouped Boolean

Tests whether the store currently has an active grouper.

Returns

isLoaded Boolean

Returns true if the Store has been loaded.

Returns

isLoading Boolean

Returns true if the Store is currently performing a load operation

Returns

isSorted Boolean

Tests whether the store currently has any active sorters.

Returns

isSuspended ( [event] ) : Boolean

Checks if all events, or a specific event, is suspended.

Parameters

Returns

last ( [grouped] ) : Ext.data.Model/undefined

Convenience function for getting the last model instance in the store.

When store is filtered, will return last item within the filter.

Parameters

Returns

load ( [options] ) : Ext.data.Store

chainable ch

Marks this store as needing a load. When the current executing event handler exits, this store will send a request to load using its configured proxy.

Upon return of the data from whatever data source the proxy connected to, the retrieved Ext.data.Model will be loaded into this store, and the optional callback will be called. Example usage:

store.load({
    scope: this,
    callback: function(records, operation, success) {
        // the operation object
        // contains all of the details of the load operation
        console.log(records);
    }
});

If the callback scope does not need to be set, a function can simply be passed:

store.load(function(records, operation, success) {
    console.log('loaded records');
});

Available since: 1.1.0

Parameters

false

Returns

loadData ( data, [append] )

Loads an array of data straight into the Store.

Using this method is great if the data is in the correct format already (e.g. it doesn't need to be processed by a reader). If your data requires processing to decode the data structure, use a Ext.data.proxy.Memory or loadRawData.

Parameters

loadPage ( page, [options] )

Loads a given 'page' of data by setting the start and limit values appropriately. Internally this just causes a normal load operation, passing in calculated 'start' and 'limit' params.

Parameters

loadRawData ( data, [append] ) : Boolean

Loads data via the bound Proxy's reader

Use this method if you are attempting to load data and want to utilize the configured data reader.

As of 4.2, this method will no longer fire the event-load event.

Parameters

Returns

loadRecords ( records, options )

Loads an array of Ext.data.Model instances into the store, fires the datachanged event. This should only usually be called internally when loading from the Ext.data.proxy.Proxy, when adding records manually use method-add instead

Parameters

false

max ( field, [grouped] ) : Object

Gets the maximum value in the store.

When store is filtered, only items within the filter are aggregated.

Parameters

Returns

min ( field, [grouped] ) : Object

Gets the minimum value in the store.

When store is filtered, only items within the filter are aggregated.

Parameters

Returns

mon ( item, ename, [fn], [scope], [options] ) : Object

Shorthand for addManagedListener. The addManagedListener method is used when some object (call it "A") is listening to an event on another observable object ("B") and you want to remove that listener from "B" when "A" is destroyed. This is not an issue when "B" is destroyed because all of its listeners will be removed at that time.

Example:

Ext.define('Foo', {
    extend: 'Ext.Component',

    initComponent: function () {
        this.addManagedListener(MyApp.SomeSharedMenu, 'show', this.doSomething);
        this.callParent();
    }
});

As you can see, when an instance of Foo is destroyed, it ensures that the 'show' listener on the menu (MyApp.SomeGlobalSharedMenu) is also removed.

As of version 5.1 it is no longer necessary to use this method in most cases because listeners are automatically managed if the scope object provided to addListener is an Observable instance. However, if the observable instance and scope are not the same object you still need to use mon or addManagedListener if you want the listener to be managed.

Parameters

Returns

this.btnListeners = myButton.mon({
    destroyable: true
    mouseover:   function() { console.log('mouseover'); },
    mouseout:    function() { console.log('mouseout'); },
    click:       function() { console.log('click'); }
});

Ext.destroy(this.btnListeners);

this.btnListeners.destroy();

mun ( item, ename, [fn], [scope] )

Shorthand for removeManagedListener. Removes listeners that were added by the mon method.

Parameters

nextPage ( options )

Loads the next 'page' in the current data set

Parameters

on ( eventName, [fn], [scope], [options], [order] ) : Object

The on method is shorthand for addListener.

Appends an event handler to this object. For example:

myGridPanel.on("itemclick", this.onItemClick, this);

The method also allows for a single argument to be passed which is a config object containing properties which specify multiple events. For example:

myGridPanel.on({
    cellclick: this.onCellClick,
    select: this.onSelect,
    viewready: this.onViewReady,
    scope: this // Important. Ensure "this" is correct during handler execution
});

One can also specify options for each event handler separately:

myGridPanel.on({
    cellclick: {fn: this.onCellClick, scope: this, single: true},
    viewready: {fn: panel.onViewReady, scope: panel}
});

Names of methods in a specified scope may also be used:

myGridPanel.on({
    cellclick: {fn: 'onCellClick', scope: this, single: true},
    viewready: {fn: 'onViewReady', scope: panel}
});

Parameters

  var panel = new Ext.panel.Panel({
      title: 'The title',
      listeners: {
          click: this.handlePanelClick,
          element: 'body'
      }
  });

 panel.body.un(...)

 handler('foo', 42, <actual event arguments>...);

false

'current'

Returns

this.btnListeners =  = myButton.on({
    destroyable: true
    mouseover:   function() { console.log('mouseover'); },
    mouseout:    function() { console.log('mouseout'); },
    click:       function() { console.log('click'); }
});

Ext.destroy(this.btnListeners);

this.btnListeners.destroy();

onAfter ( eventName, fn, [scope], [options] )

Appends an after-event handler.

Same as addListener with order set to 'after'.

Parameters

onBefore ( eventName, fn, [scope], [options] )

Appends a before-event handler. Returning false from the handler will stop the event.

Same as addListener with order set to 'before'.

Parameters

previousPage ( options )

Loads the previous 'page' in the current data set

Parameters

query ( property, value, [anyMatch], [caseSensitive], [exactMatch] ) : Ext.util.Collection

Query all the cached records in this Store by name/value pair. The parameters will be used to generated a filter function that is given to the queryBy method.

This method complements queryBy by generating the query function automatically.

This method is not affected by filtering, it will always search all records in the store regardless of filtering.

Parameters

Returns

queryBy ( fn, [scope] ) : Ext.util.Collection

Query all the cached records in this Store using a filtering function. The specified function will be called with each record in this Store. If the function returns true the record is included in the results.

This method is not affected by filtering, it will always search all records in the store regardless of filtering.

Parameters

Returns

rejectChanges

Rejects outstanding changes on all modified records and re-insert any records that were removed locally. Any phantom records will be removed.

relayEvents ( origin, events, [prefix] ) : Object

Relays selected events from the specified Observable as if the events were fired by this.

For example if you are extending Grid, you might decide to forward some events from store. So you can do this inside your initComponent:

this.relayEvents(this.getStore(), ['load']);

The grid instance will then have an observable 'load' event which will be passed the parameters of the store's load event and any function fired with the grid's load event would have access to the grid using the this keyword (unless the event is handled by a controller's control/listen event listener in which case 'this' will be the controller rather than the grid).

Parameters

this.relayEvents(this.getStore(), ['load', 'clear'], 'store');

Returns

this.storeRelayers = this.relayEvents(this.getStore(), ['load', 'clear'], 'store');

Ext.destroy(this.storeRelayers);

reload ( [options] )

Reloads the store using the last options passed to the method-load method. You can use the reload method to reload the store using the parameters from the last load() call. For example:

store.load({
    params : {
        userid : 22216
    }
});

//...

store.reload();

The initial method-load execution will pass the userid parameter in the request. The reload execution will also send the same userid parameter in its request as it will reuse the params object from the last method-load call.

You can override a param by passing in the config object with the params object:

store.load({
    params : {
        userid : 22216,
        foo    : 'bar'
    }
});

//...

store.reload({
    params : {
        userid : 1234
    }
});

The initial method-load execution sends the userid and foo parameters but in the reload it only sends the userid paramter because you are overriding the params config not just overriding the one param. To only change a single param but keep other params, you will have to get the last params from the lastOptions property:

// make a copy of the last params so we don't affect future reload() calls
var lastOptions = store.lastOptions,
    lastParams = Ext.clone(lastOptions.params);

lastParams.userid = 1234;

store.reload({
    params : lastParams
});

This will now send the userid parameter as 1234 and the foo param as 'bar'.

Parameters

remove ( records )

Removes the specified record(s) from the Store, firing the event-remove event for the removed records.

After all records have been removed a single datachanged is fired.

Parameters

removeAfterListener

Alias for unAfter.

removeAll ( [silent] ) : Ext.data.Model[]

Removes all unfiltered items from the store. Filtered records will not be removed. Individual record event-remove events are not fired by this method.

Parameters

Returns

removeAt ( index, [count] )

Removes the model instance(s) at the given index

Parameters

removeBeforeListener

Alias for unBefore.

removeFilter ( toRemove, [suppressEvent] )

Removes an individual Filter from the current filter set using the passed Filter/Filter id and by default, applies the updated filter set to the Store's unfiltered dataset.

Parameters

removeListener ( eventName, fn, [scope] ) :

chainable ch

Removes an event handler.

Parameters

Returns

removeManagedListener ( item, ename, [fn], [scope] )

Removes listeners that were added by the mon method.

Parameters

resumeAutoSync ( syncNow )

Resumes automatically syncing the Store with its Proxy. Only applicable if autoSync is true

Parameters

resumeEvent ( eventName )

Resumes firing of the named event(s).

After calling this method to resume events, the events will fire when requested to fire.

Note that if the suspendEvent method is called multiple times for a certain event, this converse method will have to be called the same number of times for it to resume firing.

Parameters

resumeEvents ( [discardQueue] )

Resumes firing events (see suspendEvents).

If events were suspended using the queueSuspended parameter, then all events fired during event suspension will be sent to any listeners now.

Parameters