ExtReact Docs Help


The documentation for the ExtReact product diverges somewhat from the documentation of other Sencha products. The sections below describe documentation for all products except where indicated as unique to ExtReact.

Terms, Icons, and Labels

Many classes have shortcut names used when creating (instantiating) a class with a configuration object. The shortcut name is referred to as an alias (or xtype if the class extends Ext.Component). The alias/xtype is listed next to the class name of applicable classes for quick reference.

ExtReact component classes list the configurable name prominently at the top of the API class doc followed by the fully-qualified class name.

Access Levels

Framework classes or their members may be specified as private or protected. Else, the class / member is public. Public, protected, and private are access descriptors used to convey how and when the class or class member should be used.

Member Types

Member Syntax

Below is an example class member that we can disect to show the syntax of a class member (the lookupComponent method as viewed from the Ext.button.Button class in this case).

lookupComponent ( item ) : Ext.Component

Called when a raw config object is added to this container either during initialization of the items config, or when new items are added), or {@link #insert inserted.

This method converts the passed object into an instanced child component.

This may be overridden in subclasses when special processing needs to be applied to child creation.


item :  Object

The config object being added.


The component to be added.

Let's look at each part of the member row:

Member Flags

The API documentation uses a number of flags to further commnicate the class member's function and intent. The label may be represented by a text label, an abbreviation, or an icon.

Class Icons

- Indicates a framework class

- A singleton framework class. *See the singleton flag for more information

- A component-type framework class (any class within the Ext JS framework that extends Ext.Component)

- Indicates that the class, member, or guide is new in the currently viewed version

Member Icons

- Indicates a class member of type config

Or in the case of an ExtReact component class this indicates a member of type prop

- Indicates a class member of type property

- Indicates a class member of type method

- Indicates a class member of type event

- Indicates a class member of type theme variable

- Indicates a class member of type theme mixin

- Indicates that the class, member, or guide is new in the currently viewed version

Class Member Quick-Nav Menu

Just below the class name on an API doc page is a row of buttons corresponding to the types of members owned by the current class. Each button shows a count of members by type (this count is updated as filters are applied). Clicking the button will navigate you to that member section. Hovering over the member-type button will reveal a popup menu of all members of that type for quick navigation.

Getter and Setter Methods

Getting and setter methods that correlate to a class config option will show up in the methods section as well as in the configs section of both the API doc and the member-type menus just beneath the config they work with. The getter and setter method documentation will be found in the config row for easy reference.

ExtReact component classes do not hoist the getter / setter methods into the prop. All methods will be described in the Methods section

History Bar

Your page history is kept in localstorage and displayed (using the available real estate) just below the top title bar. By default, the only search results shown are the pages matching the product / version you're currently viewing. You can expand what is displayed by clicking on the button on the right-hand side of the history bar and choosing the "All" radio option. This will show all recent pages in the history bar for all products / versions.

Within the history config menu you will also see a listing of your recent page visits. The results are filtered by the "Current Product / Version" and "All" radio options. Clicking on the button will clear the history bar as well as the history kept in local storage.

If "All" is selected in the history config menu the checkbox option for "Show product details in the history bar" will be enabled. When checked, the product/version for each historic page will show alongside the page name in the history bar. Hovering the cursor over the page names in the history bar will also show the product/version as a tooltip.

Search and Filters

Both API docs and guides can be searched for using the search field at the top of the page.

On API doc pages there is also a filter input field that filters the member rows using the filter string. In addition to filtering by string you can filter the class members by access level, inheritance, and read only. This is done using the checkboxes at the top of the page.

The checkbox at the bottom of the API class navigation tree filters the class list to include or exclude private classes.

Clicking on an empty search field will show your last 10 searches for quick navigation.

API Doc Class Metadata

Each API doc page (with the exception of Javascript primitives pages) has a menu view of metadata relating to that class. This metadata view will have one or more of the following:

Expanding and Collapsing Examples and Class Members

Runnable examples (Fiddles) are expanded on a page by default. You can collapse and expand example code blocks individually using the arrow on the top-left of the code block. You can also toggle the collapse state of all examples using the toggle button on the top-right of the page. The toggle-all state will be remembered between page loads.

Class members are collapsed on a page by default. You can expand and collapse members using the arrow icon on the left of the member row or globally using the expand / collapse all toggle button top-right.

Desktop -vs- Mobile View

Viewing the docs on narrower screens or browsers will result in a view optimized for a smaller form factor. The primary differences between the desktop and "mobile" view are:

Viewing the Class Source

The class source can be viewed by clicking on the class name at the top of an API doc page. The source for class members can be viewed by clicking on the "view source" link on the right-hand side of the member row.

ExtAngular 6.7.0


NPM Package





Represents a read or write operation performed by a Ext.data.proxy.Proxy. Operation objects are used to enable communication between Stores and Proxies. Application developers should rarely need to interact with Operation objects directly.

Several Operations can be batched together in a Ext.data.Batch.

No members found using the current filters


Optional Configs

batch : Ext.data.Batch

The batch for this operation, if applicable

getBatch : Ext.data.Batch

Returns the value of batch



setBatch (batch)

Sets the value of batch


batch :  Ext.data.Batch

callback : Function

Function to execute when operation completed.


records : Ext.data.Model[]

Array of records.

operation : Ext.data.operation.Operation

The Operation itself.

success : Boolean

True when operation completed successfully.

getCallback : Function

Returns the value of callback



setCallback (callback)

Sets the value of callback


callback :  Function

id : Object

The id of the operation.

getId : Object

Returns the value of id



setId (id)

Sets the value of id


id :  Object

params : Object

Parameters to pass along with the request when performing the operation.

getParams : Object

Returns the value of params



setParams (params)

Sets the value of params


params :  Object

proxy : Ext.data.proxy.Proxy

The proxy for this operation

getProxy : Ext.data.proxy.Proxy

Returns the value of proxy



setProxy (proxy)

Sets the value of proxy


proxy :  Ext.data.proxy.Proxy

records : Ext.data.Model[]

The records associated with this operation. If this is a read operation, this will be null until data is returned from the Ext.data.proxy.Proxy.

getRecords Ext.data.Model[]

Returns the Ext.data.Models associated with this operation. For read operations the records as set by the Ext.data.proxy.Proxy will be returned (returns null if the proxy has not yet set the records).

For create, update, and destroy operations the operation's initially configured records will be returned, although the proxy may modify these records' data at some point after the operation is initialized.



setRecords (records)

Sets the value of records


records :  Ext.data.Model[]

request : Ext.data.Request

The request for this operation.

getRequest : Ext.data.Request

Returns the value of request



setRequest (request)

Sets the value of request


request :  Ext.data.Request

resultSet : Ext.data.ResultSet

The ResultSet for this operation.

getResultSet : Ext.data.ResultSet

Returns the value of resultSet



setResultSet (resultSet)

Sets the value of resultSet


resultSet :  Ext.data.ResultSet

scope : Object

Scope for the callback function.

getScope : Object

Returns the value of scope



setScope (scope)

Sets the value of scope


scope :  Object

synchronous : Boolean

True if this Operation is to be executed synchronously. This property is inspected by a Ext.data.Batch to see if a series of Operations can be executed in parallel or not.

Defaults to:


getSynchronous : Boolean

Returns the value of synchronous



setSynchronous (synchronous)

Sets the value of synchronous


synchronous :  Boolean

url : String

The url for this operation. Typically this will be provided by a proxy and not configured here.

Defaults to:


getUrl : String

Returns the value of url



setUrl (url)

Sets the value of url


url :  String



Instance Methods


Aborts the processing of this operation on the proxy. This is only valid for proxies that make asynchronous requests.

allowWrite Boolean

Checks whether this operation should cause writing to occur.



Whether the operation should cause a write to occur.

constructor ( [config] )

Creates new Operation object.


config :  Object (optional)

Config object.

getError String/Object

Returns the error string or object that was set using setException



The error object

hasException Boolean

Returns true if this Operation encountered an exception (see also getError)



True if there was an exception

isComplete Boolean

Returns true if the Operation has been completed



True if the Operation is complete

isRunning Boolean

Returns true if the Operation has been started but has not yet completed.



True if the Operation is currently running

isStarted Boolean

Returns true if the Operation has been started. Note that the Operation may have started AND completed, see isRunning to test if the Operation is currently running.



True if the Operation has started


Marks the Operation as completed.

setException ( [error] )

Marks the Operation as having experienced an exception. Can be supplied with an option error message/object.


error :  String/Object (optional)

error string/object


Marks the Operation as started.

setSuccessful ( [complete] )

Marks the Operation as successful.


complete :  Boolean (optional)

true to also mark this operation as being complete See setCompleted.

wasSuccessful Boolean

Returns true if the Operation has completed and was successful



True if successful

Static Methods

override ( members ) : Ext.Base
static sta

Override members of this class. Overridden methods can be invoked via Ext.Base#callParent.

Ext.define('My.Cat', {
    constructor: function() {
        alert("I'm a cat!");

    constructor: function() {
        alert("I'm going to be a cat!");



var kitty = new My.Cat(); // alerts "I'm going to be a cat!"
                          // alerts "I'm a cat!"
                          // alerts "Meeeeoooowwww"

Direct use of this method should be rare. Use Ext.define instead:

Ext.define('My.CatOverride', {
    override: 'My.Cat',
    constructor: function() {
        alert("I'm going to be a cat!");



The above accomplishes the same result but can be managed by the Ext.Loader which can properly order the override and its target class and the build process can determine whether the override is needed based on the required state of the target class (My.Cat).


members :  Object

The properties to add to this class. This should be specified as an object literal containing one or more properties.



this class

ExtAngular 6.7.0