Releases: js-data/js-data
Releases · js-data/js-data
2.0.0-beta.8
2.0.0-beta.8 - 22 June 2015
Backwards compatible API changes
- #160 - Add "DS.change" events, fired on Resources and instances
2.0.0-beta.7
2.0.0-beta.6
2.0.0-beta.5
2.0.0-beta.5 - 27 May 2015
Breaking API changes
- #54 - feat: Call the inject and eject lifecycle hooks regardless of if the notify option is enabled
Backwards compatible API changes
- #131 - array of IDs based hasMany relations
- #132 - Allow resources to extend other resources
- #133 - Allow filtering by nested fields
- #135 - JSData caching inconsistent behaviour when ejecting items
- #138 - Collection class
- #139 - Option to specify default values of new resource instances.
Backwards compatible bug fixes
2.0.0-beta.4
2.0.0-beta.2
2.0.0-beta.2 - 17 April 2015
Updated a dependency for better umd amd/r.js support
2.0.0-beta.1
2.0.0-beta.1 - 17 April 2015
Breaking API changes
- #107 - Switch to property accessors (getter/setter) for relations links. (Relation links are no longer enumerable)
- #121 - Remove bundled Promise code (The developer must now ensure an ES6-style Promise constructor is available)
- #122 - Remove coupling with js-data-schema (You can still use js-data-schema, js-data just doesn't know anything about js-data-schema anymore)
Backwards compatible API changes
- Computed properties now support nested fields (both the computed field and the fields it depends on) e.g.
computed: { 'name.fullName': ['name.first', 'name.last', function (first, last) { return first + ' ' + last; } }
1.8.0
1.8.0 - 14 April 2015
Backwards compatible API changes
- #117 - .find skips the object in the store
- #118 - DS#find() returns items cached with DS#inject() - Thanks @mightyguava!
createInstance
will now initialize computed properties (but they won't be updated until the item is injected into the store, or unless you useInstance#set(key, value)
to mutate the instance)