Releases: danielspaniel/ember-data-change-tracker
Releases · danielspaniel/ember-data-change-tracker
v0.7.2
- use Ember.assign instead of Object.assign #35
- switch testem to run chrome headless
v0.7.1
- fixed bug where ember data did not yet have constructor.modelName prepared on EmberData 2.14+ #34
v0.7.0
Breaking Change
- renamed the
changed
method to modelChanges
#32
Where before you would do this to see model changes:
let user = store.peekRecord('user', 1);
user.set('name', 'Zippy');
user.changed(); //=> { name: ['Bob', 'Zippy']}
You would now do this:
let user = store.peekRecord('user', 1);
user.set('name', 'Zippy');
user.modelChanges(); //=> { name: ['Bob', 'Zippy']}
v0.6.2
- make all attributes and relationships last tracker value be undefined for newly created records #22
- means that any attribute or relationship set at create time or later will be considered 'changed'
v0.6.1
-fixes hasMany removeObject was not triggering isDirty/isDirtyRelations computed property #23
v0.6.0
- updates for ember-data 2.14 #21 #20
v0.5.6
- update to ember-data 2.13
v0.5.5
- changes to the order of a hasMany array will now be considered a change #15 #14 (@denzo)
v0.5.4
- once and for all fixes resetting isDirty after save for non auto save model #13
v0.5.3
- fixes isDirty not being reset properly after save #13
- bumped up ember-data -> 2.12 / model-fragments => 2.11.2