Deeply nested backbone.js objects cause errors?

Question

I am working on a project using the following namespacing scheme:

var abc = {};
abc.models = {};
abc.views = {};

abc.models.Collection = Backbone.Collection.extend({});

When I seek to create a new collection I receive the following error

var collection = new abc.models.Collection({this:"that"});
TypeError: Object #<Object> has no method '_reset'

when I moved the constructor to abc.Collection the error stopped and everything started working as needed.

Can someone please help me understand why this is?

I should also add that this is part of a multi-file application where each file is wrapped with the following:

(function($, abc){

//module contents here

}(jQuery, abc));

Works for me, check the working jsFiddle the issue should be somewhere else. Which Backbone version are you using? — fguillen
– fguillen, Commented Aug 21, 2012 at 14:32
Same version than in my jsFiddle.. check it out, why is working there? — fguillen
– fguillen, Commented Aug 21, 2012 at 14:49
That's interesting. It could be there is something funky happening in the abc namespace that is messing with things. I think for now I will make shallow these constructors. — Dean Peterson
– Dean Peterson, Commented Aug 21, 2012 at 14:54
There is an internal _reset method in Backbone.Collection but there's not enough information here to know what's going wrong. — mu is too short
– mu is too short, Commented Aug 21, 2012 at 17:46
I've been doing a lot of refactoring today. It appears the issues have cleared up. I just wish I knew exactly why. Thanks for you input. — Dean Peterson
– Dean Peterson, Commented Aug 21, 2012 at 21:58

dnozay · Accepted Answer · 2013-10-21 22:45:40Z

3

this works:

var abc = {};
abc.models = {};
abc.views = {};
abc.models.Collection = Backbone.Collection.extend({});
var collection = new abc.models.Collection([], {});

whereas this trips with Uncaught TypeError: Object #<Object> has no method '_reset':

var abc = {};
abc.models = {};
abc.views = {};
abc.models.Collection = Backbone.Collection.extend({});
var collection = abc.models.Collection([], {});

The difference is not calling the constructor with new.

answered Oct 21, 2013 at 22:45

dnozay

24.4k6 gold badges85 silver badges105 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Roger · Accepted Answer · 2012-08-21 14:29:34Z

0

The first argument to a new Backbone Collection is an array of models and then a hash of options. Are you trying to pass in an array of models, if not then pass in the empty array: []

answered Aug 21, 2012 at 14:29

Roger

3021 silver badge10 bronze badges

1 Comment

Dean Peterson Over a year ago

That's not the issue. You can pass a simple object and if there is a model assigned to the collection, it will create the model on the fly. The question here is why does the creation before fail when the Constructor is 2 levels deep into an object as opposed to 1.

Collectives™ on Stack Overflow

Deeply nested backbone.js objects cause errors?

2 Answers 2

Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related