0.10.0

Changes

• 84fae6c Fix ordering problems in relations
• 0731ff3 Backbone 1.2.1 compatible (add _removeModels override)

0.9.0

Changes

• 42b158d Add getIdsToFetch to Backbone.RelationalModel
• b7e7123 getAsync (the successor of fetchRelated) now return a single promise, instead of an array of request objects.
• #467: Improve lazy loading implementation. Add getAsync to Backbone.RelationalModel, which always return a single promise that resolves with the attribute's content, and remove fetchRelated

Breaking Changes

• Removed fetchRelated in favor of getAsync

0.8.8

Changes

• #419: Proper return values for single models on collection methods for Backbone 1.1.0
• 4113c69 Backbone.Relational.store.unregister now also accepts a collection or a model type
• #427: Fix firing explicit change events
• #215 Add direct support for AMD, CommonJS, require, etc.

Potentially Breaking Changes

• #411: Don't add models without an id to the store

0.8.7

Changes

• 8371089: Change return types for Collection methods to match Backbone 1.1.0
• #376: Include ids of unregistered models (not fetched or otherwise) in toJSON
• 8371089: Add findModel

0.8.6

Changes

• #322: Remove keySource value after a `setl
• #345: Add find, a shortcut to findOrCreate with create: false
• #345: Add lodash compatibility (doesn't have an explicit findWhere)
• #349: Event ordering: maintain the originally intended order when process gets called more than once.
• #362: Add support for deep subModelType hierarchies.
• #380: Fix pop on an empty collection.
• #370: Relations can now be a property or a function.
• 7f1dc51: relatedModel and collectionType can now be defined as a function as well.

0.8.5

Changes

• Supports Backbone 1.0.0
• #191: if includeInJSON is equal to the model's idAttribute, "missing" models will be included in the JSON to avoid data loss
• #201: Added Backbone.Store.removeModelScope method
• #273: Improve merging of relations between super/subModels
• #295: Check (and error on) duplicate ids when explicitly setting the idAttribute
• #320: Use merge: true by default on Collection.reset

0.8.0

Changes

• General performance improvements, refactored HasMany.onChange to eliminate unnecessary events.
• Implemented the add, merge and remove options on Collection.add when working with RelationalModels. This also works when using set to change the key on nested relations.
• findOrCreate now takes a parse option, analogous to the Backbone.Model constructor. It defaults to false
• Added a parse option to relations

Breaking Changes

• The update:<key> event has been removed, in favor of handling everything using "standard" change:<key> events.
• The update option on findOrCreate has been renamed to merge, since its behavior corresponds with merge on Collection.add (and not with update on Collection.reset).

0.7.1

Changes

• Compatible with Backbone >= 0.9.10
• Implemented the autoFetch property for relations
• Added the update option to findOrCreate

0.7.0

Changes

• Compatible with Backbone >= 0.9.9
• #180: no longer allow multiple instances of RelationalModels with the same type, and the same id

0.6.1

Changes

• #215 Fix export issue with require.js