ExtReact Docs Help

Introduction

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
protected

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.

Parameters

item :  Object

The config object being added.

Returns
Ext.Component

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.

ExtReact 6.6.0


top

Ext.data.identifier.Generator alias: data.identifier.default

NPM Package

@sencha/ext-react

Hierarchy

Ext.Base
Ext.data.identifier.Generator

Summary

This class is a base for all id generators. It also provides lookup of id generators by their id.

Generally, id generators are used to generate a primary key for new model instances. There are different approaches to solving this problem, so this mechanism has both simple use cases and is open to custom implementations. A Ext.data.Model requests id generation using the Ext.data.Model#identifier property.

The following types of identifiers are provided:

In most cases (other than uuid), the server is the only party that can generate authoritative id values. This means that any id generated by an identifier should be consider "provisional" and must eventually be reconciled with the server. This makes a uuid very attractive as an identifier because they are designed to be generated in a distributed manner and therefore never require reconciliation.

It is common for id values to be generated as increasing integer values (1, 2, etc.) by the server when records are inserted. A Ext.data.identifier.Negative identifier may be useful as it generates client-side values of -1, -2, etc.. These values are of the same data type (integer) and so can typically be read by servers using typed languages (such as Java or C#) and easily recognized as provisional.

In the end, the choice of identifier strategy requires agreement between client and server.

Identity, Type and Shared Generators

It is often desirable to share Generators to ensure uniqueness or common configuration. This is done by giving Generator instances an id property by which they can be looked up using the dataIdentifier method. To configure two Ext.data.Model classes to share one Ext.data.identifier.Sequential id generator, you simply assign them the same id:

Ext.define('MyApp.data.MyModelA', {
    extend: 'Ext.data.Model',
    identifier: {
        type: 'sequential',
        id: 'foo'
    }
});

Ext.define('MyApp.data.MyModelB', {
    extend: 'Ext.data.Model',
    identifier: {
        type: 'sequential',
        id: 'foo'
    }
});

To make this as simple as possible for generator types that are shared by many (or all) Models, the Generator types (such as 'sequential' or 'uuid') are also reserved as generator ids. This is used by the Ext.data.identifier.Uuid which has an id equal to its type ('uuid'). In other words, the following Models share the same generator:

Ext.define('MyApp.data.MyModelX', {
    extend: 'Ext.data.Model',
    identifier: 'uuid'
});

Ext.define('MyApp.data.MyModelY', {
    extend: 'Ext.data.Model',
    identifier: 'uuid'
});

This can be overridden (by specifying the id explicitly), but there is no particularly good reason to do so for this generator type.

Creating Custom Generators

An id generator should derive from this class and implement the generate method.

To register an id generator type, a derived class should provide an alias like so:

Ext.define('MyApp.data.identifier.Custom', {
    extend: 'Ext.data.identifier.Generator',
    alias: 'data.identifier.custom',
    config: {
        configProp: 42 // some config property w/default value
    }

    generate: function () {
        return ... // a new id
    }
});

Using the custom id generator is then straightforward:

Ext.define('MyApp.data.MyModel', {
    extend: 'Ext.data.Model',
    identifier: 'custom'
});
// or...

Ext.define('MyApp.data.MyModel', {
    extend: 'Ext.data.Model',
    identifier: {
        type: 'custom',
        configProp: value
    }
});

It is not recommended to mix shared generators with generator configuration. This leads to unpredictable results unless all configurations match (which is also redundant). In such cases, a custom generator with a default id is the best approach.

Ext.define('MyApp.data.identifier.Custom', {
    extend: 'Ext.data.identifier.Sequential',
    alias: 'data.identifier.custom',

    config: {
        id: 'custom',
        prefix: 'ID_',
        seed: 1000
    }
});

Ext.define('MyApp.data.MyModelX', {
    extend: 'Ext.data.Model',
    identifier: 'custom'
});

Ext.define('MyApp.data.MyModelY', {
    extend: 'Ext.data.Model',
    identifier: 'custom'
});

// the above models share a generator that produces ID_1000, ID_1001, etc..
No members found using the current filters

configs

Optional Configs

id : String

The id for this generator.

getId : String

Returns the value of id

Returns

String

setId (id)

Sets the value of id

Parameters

id :  String

properties

Instance Properties

factoryConfig : Object

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

isGenerator : Boolean

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

methods

Instance Methods

constructor ( [config] )

Initializes a new instance.

Parameters

config :  Object (optional)

Configuration object to be applied to the new instance.

generate Number/String
abstract abs

Generates and returns the next id. This method must be implemented by the derived class.

Returns

:Number/String

The next id.

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!");
    }
});

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

        this.callParent(arguments);

        alert("Meeeeoooowwww");
    }
});

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!");

        this.callParent(arguments);

        alert("Meeeeoooowwww");
    }
});

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).

Parameters

members :  Object

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

Returns

:Ext.Base

this class

ExtReact 6.6.0