pass-through options to Backbone.Store#unregister when called as
listener to models 'destroy'
test: change events should not fire on new items in Collection#set
Two tests showing Collection reset/set should both link related objects properly
Merge pull request #318 from elasticsales/collection-set-triggers-change

failing test: change events should not fire on new items in Collection#set
Merge pull request #320 from elasticsales/collection-set-vs-reset

Two tests (1 failing) showing Collection reset/set should both link related objects
Use `merge: true` by default for Collection.reset. Ref #320
Simpler test added for `merge: true` on Collection.reset.

Revert "Merge pull request #320 from elasticsales/collection-set-vs-reset"

This reverts commit c31ea90071753f1f475f780ef4143229d5a28f19, reversing
changes made to 9b52eb220bb86a2da5e41c08e55b76a1f2108871.
Add a note in the change log about the changed default for `merge` on `reset`
Docs: add a description for `removeModelScope`
Backbone-relational 0.8.5; compatible with Backbone 1.0.0
Failing test case where BBR drops a 'change' event.
The sort event should be deferred with add events to keep events in  order (sort after add)
No 'module' in nodejs/requirejs environment
Ensuring attributes hash does not get changed by findOrCreate

- using clone to prevent modification of original attributes hash
- adding test to cover this scenario
Merge pull request #331 from ClemensSchneider/pass_through_options_on_unregister

pass-through options to Backbone.Store#unregister when called as listener to models 'destroy'
Merge pull request #332 from idanz/master

sort event should also be queued when the add event is queued
Change `change` event test to at least fix/reflect the current situation
when using dotNotation, return undefined if the path cannot be expanded
Merge pull request #339 from dvrenterghem-ibuildings/master

Ensure attributes hash does not get changed by findOrCreate
Add model.find, findOrCreate with create: false