Are there ever going to be useful events on Ext.data.Model ?

[plleeuwm]

Currently in the 4.2 beta and the lower the Ext.data.Model methods of afterEdit, afterReject, afterCommit just call methods on the actual store object(s) if there is one linked. If you have a model without a store you are SOL, the only event that gets fired from Model is of all things 'idchanged'. Are there any plans to put these events into models?

[mitchellsimoens]

You could easily add events, for example a datachanged when you hit set (disclaimer: needs to be furthered to handle an object)

Ext.define('Override.data.Model', {
    override : 'Ext.data.Model',

    set : function(fieldName, newValue) {
        var oldValue = this.get(fieldName),
            ret      = this.callParent([fieldName, newValue]);

        this.fireEvent('datachanged', this, fieldName, newValue, oldValue);

        return ret;
    }
});

Ext.define('MyModel', {
    extend : 'Ext.data.Model',

    fields : ['foo']
});

Ext.application({
    name : 'Test',

    launch : function() {

        var model = new MyModel({
            foo : 'bar'
        });

        model.on('datachanged', function(record, fieldName, newValue, oldValue) {
            console.log('data changed', fieldName, newValue, oldValue);
        });

        model.set('foo', 'mitch');

    }
});

[plleeuwm]

You could easily add events, for example a datachanged when you hit set (disclaimer: needs to be furthered to handle an object)

Ext.define('Override.data.Model', {
    override : 'Ext.data.Model',

    set : function(fieldName, newValue) {
        var oldValue = this.get(fieldName),
            ret      = this.callParent([fieldName, newValue]);

        this.fireEvent('datachanged', this, fieldName, newValue, oldValue);

        return ret;
    }
});

Ext.define('MyModel', {
    extend : 'Ext.data.Model',

    fields : ['foo']
});

Ext.application({
    name : 'Test',

    launch : function() {

        var model = new MyModel({
            foo : 'bar'
        });

        model.on('datachanged', function(record, fieldName, newValue, oldValue) {
            console.log('data changed', fieldName, newValue, oldValue);
        });

        model.set('foo', 'mitch');

    }
});

But this logic already exists in store why would we want to duplicate it?

model.set('foo', 'mitch');
model.set('foo', 'mitch');

Would fire datachanged twice. The stores update event logic already handles this.

***
Yes I know we can have overrides that can do anything to the code but I think that this should be handled at the framework level. If you guys have no intention adding the events we can add them ourselves which is fine with us. I'd be worried about if we publish these events in our code developers rely on these events but then in 4.2 you guys publish something very similar. That would start us down the path of a complicated deprecation and refactoring process.

[plleeuwm]

Here is my proposed solution to the problem if there there will be no work done to improve the model event system. There probably is some bugs in it but I whipped it in less than 30 mins. It is a complete hack of a bad design imo.

Ext.override(Ext.data.Model, {
    relayStoreEvents: function(events) {
        if (!this._eventsStore) {
            this._eventsStore = new Ext.data.Store({
                model: this.self
            });
            this.join(this._eventsStore);
            this.relayEvents(this._eventsStore, events || ['update']);
        }
    }
});

I have designed a record based form with has it's saving, reading and writing and other logic go through the model instead of the Form submit actions. My problem is that there are no useful update events on the model itself without a store.

But I can do something like :

Ext.define('RecordForm', 
    loadRecord: function(rec) {
    var ret = this.callParent(arguments);
    rec.relayStoreEvents();
    return ret;
    }    
}

In another part of the code I can publish the update events on the rec through the RecordForm.

[slemmon]

+1