Initialization order change when id's are present about backbone-relational HOT 4 CLOSED

Hmm.. I'd expect a different order altogether, seeing as the comparator is called in Backbone.Collection._add for each model right after creation. I'll look into it.

from backbone-relational.

Can't seem to replicate this (neither in Firefox or Chrome), at least not with the versions of Backbone (0.5.3) and Underscore (1.1.7) I'm testing with. Do you still experience this behavior? With ids present, I get the following results:

first mother
child initialized
child initialized
comparator called; model.id=j1
comparator called; model.id=j2
mother initialized
second mother
child initialized
child initialized
comparator called; model.id=j3
comparator called; model.id=j4
mother initialized

from backbone-relational.

Come to think of it, this would probably have been fixed for you by upgrading to backbone-relational 0.4, since collection.add and collection.remove are also synced as of that version?

from backbone-relational.

No, I don't have the behavior now (least not with the test case). I'll look at the original code too, but I think you can consider this issue closed.

from backbone-relational.