Re: Correct way to push to an array in a model

Yes, what you've written is OK, although a shallow copy will be perfectly fine that is, curUnsavedChanges = that.model.unsavedChanges.concat([{description: description}]) or so. Yes, there will indeed be new dedicated change types as planned at https://issues.fluidproject.org/browse/FLUID-3504

RE: Correct way to push to an array in a model

Hi all, I'm also interested in seeing what the "right" way to handle such a situation is. I recently encountered a case which was similar. I needed to create a fresh array and then add that to a model path, though I will almost certainly need to make modifications to that path in the future so

Second Level Navigation in Doc Files

Hi everyone, I have been working on restructuring the content of ILDH. As part of this work, some of the current tabs on the site (Accessible Standardized Testing and Inclusive

Re: CLA service for Fluid GitHub repos

Something that we may want to take into consideration is the implementation language/technology (if we end up hosting an instance ourselves). cla-assistant is JavaScript Node.js with MongoDB for persistence and clahub is Ruby on Rails Simon From: