[CLOSED][4.0.0] Ext.AbstractComponent.getPlugin() issue?

[damien.corpataux]

I can't acces an AbstractComponent child class plugins using the Ext.AbstractComponent.getPlugin(id) method.

The method returns undefined. Nevertheless, I can call getPlugin() without argument and the method returns the (only) registered plugin.

Code excerpt:

    Ext.define('SomeModel', {
    extend: 'Ext.data.Model',
    fields: [{name: 'id', type: 'int'}],
        validations: []
    });

    var composition_grid = new Ext.grid.Panel({
        id: 'abc-grid',
        width: 800,
        height: 200,
        plugins: [new Ext.grid.plugin.RowEditing({id:'rowediting'})],
        store: Ext.create('Ext.data.Store', { model: 'SomeModel' }),
        columns: [{
            header: "ID",
            dataIndex: 'id',
            editor: {
                xtype: 'textfield',
                allowBlank: false
            }
        }],
        dockedItems: [{
            xtype: 'toolbar',
            items: [{
                text: 'Test',
                handler: function(){
                    console.log('getPlugin():', this.up('gridpanel').getPlugin();
                    console.log('getPlugin('rowediting'):', this.up('gridpanel').getPlugin('rowediting');
                }
            }]
        }]
    });

[kender]

hi, try to use "itemId" instead of "id":

[...]
plugins: [new Ext.grid.plugin.RowEditing({itemId:'rowediting'})],

and this works:

this.up('gridpanel').getPlugin('rowediting');

[damien.corpataux]

Thank you for your anwser.

After testing, both itemId and id config options do not work.


After a brief dip into AbstractComponent source, it turns out that using the undocumented pluginId internal does the trick as an (ugly) workaround.

I don't have time to dig further. However, it seems reasonable that the pluginId property should be set from the config options' id or itemId at instanciation time.

I believe is a problem here, because it is common to compose Components with Plugins using the config options flavour - and fetching a plugin using its id seems to be quite common.

[...]
plugins: [new Ext.grid.plugin.RowEditing({pluginId:'rowediting'})],

this.up('gridpanel').getPlugin('rowediting');

[evant]

You want to specify the pluginId:

Ext.require('*');
Ext.define('SomeModel', {
    extend: 'Ext.data.Model',
    fields: [{
        name: 'id',
        type: 'int'
    }]
});

Ext.onReady(function(){


    var composition_grid = new Ext.grid.Panel({
        width: 800,
        height: 200,
        renderTo: document.body,
        plugins: [new Ext.grid.plugin.RowEditing({
            pluginId: 'rowediting'
        })],
        store: Ext.create('Ext.data.Store', {
            model: 'SomeModel'
        }),
        columns: [{
            header: "ID",
            dataIndex: 'id',
            editor: {
                xtype: 'textfield',
                allowBlank: false
            }
        }],
        dockedItems: [{
            xtype: 'toolbar',
            items: [{
                text: 'Test',
                handler: function(){
                    console.log(this.up('gridpanel').getPlugin('rowediting'));
                }
            }]
        }]
    });
});

[damien.corpataux]

Thank you for wiping my doubts.

It would help to find a reference to pluginId in the API Doc.


Regards

[kender]

yes "pluginId" is right..
sorry, I thought about pluginId and I write itemID