pass-through options to Backbone.Store#unregister when called as
listener to models 'destroy'
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)
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
Add lodash compat.

It doesn’t have findWhere. This patch makes BB-rel compatible with lodash.
Backbone.BlockingQueue.process() copies/resets the queue before processing

This maintains the originally intended order of events when process gets
called more than once.

Previous Behavior
=================

process() starts with events ['A1', 'A2', 'A3']. A handler of 'A2' calls
.set() on a model, this ends up queuing 'B1' and 'B2'.

The end of that .set() call starts processing and runs 'A3', 'B1', 'B2'.

final result 'A1', 'A2', 'A3', 'B1', 'B2'

New Behavior
============

process() starts with events ['A1', 'A2', 'A3']. A handler of 'A2' calls
.set() on a model, this ends up queuing 'B1' and 'B2'.

The end of that .set() call starts processing and runs 'B1', 'B2'. When
the call stack gets back to the first process() it runs 'A3'

final result 'A1', 'A2',  'B1', 'B2', 'A3'
If the events didn't have to be queued, this is the order they would
have fired in.
Removed options.url in RelationalModel.findOrCreate

The url attribute was cascading to nested models
Add `relational:unregister` optional event.

This is very useful if you want to destroy a relation by yourself.

This helps Chaplin (http://chaplinjs.org) since we need to dispose all model properties and relations on every next controller action.
Unsubscribe from collection correctly.
Fixes #360. Adds support for deep subModelType hierarchies.

Recursively resolves the appropriate subModelType to instantiate in
'Backbone.RelationalModel.build'. This allows subModelTypes to in turn declare
their own subModelTypes.
Merge pull request #353 from paulmillr/patch-2

Add `relational:unregister` optional event.
Merge pull request #349 from paulmillr/patch-1

Add lodash compat.
Merge pull request #345 from michaelmior/model-find

.find() shortcut
Merge pull request #350 from courseload/master

Backbone.BlockingQueue.process() copies/resets the queue before proceing