Releases: js-data/js-data
Releases · js-data/js-data
1.5.6
1.5.6 - 07 March 2015
Backwards compatible bug fixes
- Fixed loading of the optional js-data-schema
1.5.5
1.5.5 - 07 March 2015
Other
- Re-wrote a good amount of the code to use ES6. Now using Babel.js to transpile back to ES5.
1.5.4
1.5.4 - 05 March 2015
Backwards compatible bug fixes
- #72 - bug: items injected via a relationship fail to fire notifications (fixed more cases of this happening)
1.5.3
1.5.3 - 05 March 2015
Backwards compatible bug fixes
- #35 - beforeInject not called on relationships
- #72 - bug: items injected via a relationship fail to fire notifications
1.5.2
1.5.2 - 02 March 2015
Backwards compatible bug fixes
- Now using
DSUtils.copy when saving "original" attributes so changes can be computed properly
1.5.1
1.5.1 - 02 March 2015
Backwards compatible bug fixes
- #66 - "saved" and "lastSaved" method seems to be a misnomer
- #69 - Using resource base class w/additional properties has some side effects
- #70 - "lastSaved" timestamp changes too often
Other
- Removed use of
DSUtils.copy in the event hooks. This should increase performance quite a bit.
1.5.0
1.5.0 - 27 February 2015
Backwards compatible API changes
- #17 - feat: Load relations based on local field name
Backwards compatible bug fixes
- #62 - getAdapter when called from a Resource fails
- #65 - internal emit api was not updated to use Resource instead of Resource.name like the lifecycle hooks were
1.4.1
1.4.1 - 26 February 2015
Backwards compatible bug fixes
-
- Two possible error cases in DS#find
1.4.0
1.4.0 - 24 February 2015
Backwards compatible api changes
- #51 - Allow resource instances to be created from a base class
1.3.0
1.3.0 - 11 February 2015
Backwards compatible api changes
- #50 - Added a
DS#is(resourceName, instance) or Resource#is(instance) method to check if an object is an instance of a particular resource
Backwards compatible bug fixes
- When items are ejected cached collection queries are now checked to see if all the cached items from that query are gone, and if so, the cache query is deleted
