JsonStore forces proxy type "Ajax" despite definitions in a new class

[luismerino]

REQUIRED INFORMATION




Ext version tested:

• Sencha Touch 2.0PR3

Description:

• A store that extends from JsonStore will be created with ajax proxy by default, ignoring any other proxy declaration made.

Steps to reproduce the problem:

• Create a store that extends from JsonStore
• Add a proxy property with localstorage type for instance
• Create an instance of this new store and retrieve its proxy "getProxy().type"

The result that was expected:

• "localstorage"

The result that occurs instead:

• "ajax"

Test Case:

    Ext.define('Pistachio.store.Events', {
        extend: 'Ext.data.JsonStore',
        storeId: 'Events',
        proxy: {
            type: 'localstorage',
            id: 'example-events'
        }
    });


    console.log(Ext.getStore('Events').getProxy().type) // outputs "ajax"

Possible fix:

• not provided

[mitchellsimoens]

Looking at the source for the JsonStore, the proxy is checked on the config so therefore if you wanted to override the functionality you would have to do this:

Ext.define('Pistachio.store.Events', {
    extend: 'Ext.data.JsonStore',
    
    constructor : function(config) {
        if (!config) {
            config = {};
        }
        
        Ext.applyIf(config, {
            type : 'localstorage',
            id   : 'example-events' //wouldn't use a set id unless you are only going to have one instance
        });
        
        this.callParent([config]);
    }
});

[luismerino]

Ok, but perhaps using JsonStorage defaults to ajax and it probably shouldn't, since AbstractStore does not nor Store itself. This, at the very least, leads to confusion.

In any case, I am forced to use id I believe:

if (this.id === undefined) {

Ext.Error.raise("No unique id was provided to the local storage proxy. See Ext.data.proxy.LocalStorage documentation for details");
}

[mitchellsimoens]

Yes you are forced to use id but if you have one set in the class definition then that id will be shared among all instances

[luismerino]

True that. But that's not question. Now that you guys know what I mentioned above my job is done

[TommyMaintz]

This has been fixed as part of the Data Package cleanup and will be part of the next Touch 2.0 release. Thanks for the report again!