3 ms·
Both of our apps did not work anymore after the update. Does Renamed Collection's "update" to set, for parallelism with the similar model.set(), and contrast
by frankblizzard 14y ago
Both of our apps did not work anymore after the update.
Does
Renamed Collection's "update" to set, for parallelism with the similar model.set(), and contrast with reset. It's now the default updating mechanism after a fetch. If you'd like to continue using "reset", pass {reset: true}.
mean that now collections don't fire the 'reset' event anymore? Should we use collection.on('set', ...) instead? Because I think there are a lot of apps in the wild relying on the collection.on('reset', ...) syntax out there as this is seen in most of the tutorials.
- jashkenas 14y agoNot quite -- the default has changed. It means you should call: collection.fetch({reset: true}) ... and everything should continue to work as it did before. That said, this isn't the best forum for debugging help -- you'll probably have faster responses asking on IRC.
- frankblizzard 14y agook thanks for clarification. and for backbone in general ;)
- zeckalpha 14y agoThis helped me, too. Thanks!