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


top

Release Notes ExtReact 6.5.3

Support for Ext JS 6.5.3 enhancements and new component - SplitButton

reactor-kitchensink

  • Added examples of the SplitButton component

reactor 1.1.2

This release contains the following bug fixes:

  • Function props are now properly rebound when updated during rendering. This fixes the issue posted here in the ExtReact forum.
  • Bug: "Variable isDelete undefined in ExtJSComponent#_mergeConfig." This caused an error when attempting to add or remove columns from a grid when rerendering.
  • Bug: "TypeError: Object doesn't support property or method 'forEach' at Anonymous function". This error would show up in the debugger when using ExtReact in Edge or Internet Explorer.

Of these changes, the first has the most potential to impact existing code. ExtReact previously ignored updates to props whose values are functions (typically event handlers) when rerendering. While defining event handler functions inside of the render function is generally discouraged in react, it is still supported.

Here is an example that illustrates the bug:

class Counter extends Component {
    state = { count: 0 };

    render() {
        const count = this.state.count

        return (
            <div>
                <p>{count}</p>
                <Button text="Go" handler={() => {
                    this.setState({count: count + 1})
                }}/>
            </div>
        )
    }
}

In this example, clicking the button should increment the displayed count each time. Each time render is called, the button's handler function should be updated. This was not the case in reactor 1.1.0. The count would get stuck at 1 due to the handler function not being updated. This is fixed in reactor 1.1.1.

This fix may cause your app to behave differently if it relies on handler functions not being updated during rerendering. Fixing this bug actually exposed a few issues in the ExtReact KitchenSink, which we've also fixed. We suggest you review your code to see if it inadvertently relies on this behavior. We also suggest defining handler functions using ES7 property initializers instead of defining them in the render function. For example, the example would be better written as:

class Counter extends Component {
    state = {count: 0};

    incrementCount = () => {
        this.setState({ count: this.state.count + 1 });
    };

    render() {
        const count = this.state.count

        return (
            <div>
                <p>{count}</p>
                <Button text="Go" handler={this.incrementCount} />
            </div>
        )
    }
}

Finally, while reactor-webpack-plugin and reactor-babel-plugin have been updated to version 1.1.1 as well, no changes were made. We aim to keep the version numbers in sync for all reactor packages to avoid confusion about compatibility.

Release Notes for ExtReact 6.5.1

Support for Ext JS 6.5.1 component enhancements

reactor 1.1.0

  • You can now render React components inside Grid cells using the Column component's renderer prop or the new RendererCell component.
  • The responsive plugin is automatically added to any ExtReact component with a responsiveConfig prop.
  • The launch function now passes the viewport DOM element as a parameter to the callback function. This makes it easier to use react-hot-loader. See updated reactor-boilerplate for an example of this in action.
  • New renderWhenReady higher-order component makes it easier to build libraries based on ExtReact. When root ExtReact components are wrapped in renderWhenReady, the launch function is not needed as long as your app does not set the fullscreen prop to true on any components.
  • Added support for react-test-renderer and jest. Boilerplate projects now use jest for the npm test script.
  • You can now use component names in selectors when using Sencha Test
  • Fixed a bug that caused new children added to the first position in an existing container to be rendered in the wrong position.
  • Fixed a bug that prevented updates to the className prop from being applied to the DOM.
  • Fixed a bug that caused incorrect component names to be rendered in React dev tools' virtual DOM view.
  • Fixed a bug that prevented componentWillUnmount from being called on children of ExtReact components
  • Fixed a bug that prevented componentWillUnmount from being called on components rendered by tpl prop callbacks

reactor-webpack-plugin

  • New treeShaking options allows you to disable tree shaking in development builds to improve build times. When treeShaking is set to false, all ExtReact components are included in the build.

generator-ext-react (Yeoman Generator)

  • Typescript is now supported
  • Jest is now supported when using JavaScript
  • react-hot loader is now supported when using JavaScript
  • You can omit example code to create a minimal starter app.
  • Fixed a bug that prevented new projects from being created when yo is not installed globally
  • The generated README.md is now customized based on yeoman input parameters.

reactor-kitchensink

  • Added more examples of the Panel component
  • Added an example of a multi-step Wizard.
  • All grid examples have been updated to use Column's renderer prop and RendererCell where applicable.

Boilerplates

  • Added react-hot-loader to reactor-boilerplate and reactor-modern-boilerplate
  • All boilerplates now automatically find an open port starting with 8080.
  • npm "prod" script now uses static-server instead of webpack-dev-server.

ExtReact 6.5.2