Javascript arrays and Meteor session

Question

I have made an interesting observation. When trying to update an array that is stored in the Meteor session storage, the following code will not propagate the changes:

Answer 1

I believe this is the same as this situation in Backbone.js. In order for the change event to be triggered, Meteor needs to have a new reference for the array, not just an updated copy of the old one.

In brief, in order to have the 'correct' behaviour, you'll need to clone the array, make the changes you want, and then do Session.set('foo', myCopiedArray).