Dirty checking of properties

[bookshelf]

Dirty checking of properties

[tgriesser]

Yep - at one point I had something for this where you could do:

userTreed.save({state: 'committed'}, {patch: true})

but then I ended up removing it in favor of saving the entire model - I forget why, but I think I had a reason at the time.

Anyway, since having done that, I've found that it'd be useful to have this functionality... but I was thinking of renaming the option sent to partial: true just so it's not confusing. Does that seem like it'd make sense?

[kubino]

Hi Tim, I think both scenarios are useful in some situations. Having a simple switch (dirty check/entiry update) would be probably the best solution, but might be tricky to implement. So being explicit like this userTreed.save({state: 'committed'}, {partial: true}) is quite fine for me...

Not really sure about naming conventions :) Partial make sense, you can maybe use enumeration instead of bool. Something like updateMode - default(row) / manual / dirtyCheck ....

best
Jakub

[tgriesser]

Hey @kubino - this should now be possible in 0.3.0 with the {patch: true} method:

userTreed.save({state: 'committed'}, {patch: true});

or

userTreed.save(userTreed.changed, {patch: true});

...if you only want to update the changed properties in the model. For now, I'm going to keep the options flags as simple as I can, so there's not too many features to support off the bat, especially when they're not too difficult to implement yourself. Hope this works!