Backbone.js Collection.create and overridden Model.set

Question

I have a backbone model where I have changed the set method to calculate extra attributes on every set of the model.

According to the docs this should be the way to call super in order to make sure the model is actually saved.

Backbone.Model.prototype.set.call(this, attributes, options);

And it works just as expected, unless I use Collection.create.

My custom set method gets run, but I think the original does not since the collection remains empty. The server receives the correct data and sends the right data back. On both occasions my method gets executed, but the collection is still empty.

Can I change the super call to make it work with Collection.create or is there another way to do the same thing?

Is an exception being thrown along the way, perhaps? Have you checked your console to make sure this is not the case? — Brian Genisio
No exceptions what so ever. That would have made it easier, but sadly it just fails silently. — Mathias Nielsen

Mathias Nielsen Mathias Nielsen · Accepted Answer · 2011-10-01T12:03:11

Just as I thought, I missed something. When overriding Model.set() one must put return this; at the end.

So a model should look like this:

var MyModel = Backbone.Model.extend({
    set: function(attributes, options) {
        // Custom code...
        return Backbone.Model.prototype.set.call(this, attributes, options);
    }
});

Backbone.js Collection.create and overridden Model.set

2 Answers