Inconsistent behavior between Asset.each and Asset.find about spine HOT 7 CLOSED

Thanks, I've pushed a change to fix this (CS branch).

You have to call save() on the instance to save attributes, that's kinda the point ;) - or maybe I'm misunderstanding?

from spine.

I want to set attributes on the model that I don't want persisted to the server. For example, I'm storing a count with my Item models, so that the view for the Item can display its count. The count is calculated by a controller, and I don't want to persist it. What's the correct approach to storing the count with a model?

from spine.

Side note: Backbone has Model.save and Model.set. The save method is like Spine's save: it persists the new attributes. The set method sets attributes on the Model without persisting them (which is what I'm looking for here).

from spine.

Ok, so you want to save models without triggering ajax requests? One way to do this is with Spine.Ajax.disable()

Spine.Ajax.disable -> instance.save()

from spine.

But I still want to persist everything else, not disable Ajax completely. Is this a clean way to temporarily disable it?

from spine.

Have a closer look at that example - it only disables it for that specific
save (any save in the callback function).

On Mon, Aug 1, 2011 at 5:41 PM, chetan51 <
[email protected]>wrote:

But I still want to persist everything else, not disable Ajax completely.
Is this a clean way to temporarily disable it?

Reply to this email directly or view it on GitHub:
https://github.com/maccman/spine/issues/83#issuecomment-1704929

Alex MacCaw

+12147175129
@maccman

http://alexmaccaw.co.uk | http://www.leadthinking.com | http://socialmod.com

from spine.

Ah, I didn't realize it's in a callback function. Thanks!

from spine.