allow user to supply which fields to suppres/transmit when saving a model
iterate over the proper thing
properly perform the whitelist/blacklist of attribute
add whitelist/blacklist to local storage adapter
refactor
remove empty lines
update docs
adding new filters ceil, floor, round, precision, fixed, and commafy, and correspoding tests
fixing precision and fixed to be a little cleaner, and updating tests. all passing
adding corresponding documentation for new filters
Document data-route-params binding
specify joins params
Merge pull request #955 from rmosolgo/rm/doc-data-route-params

Document data-route-params binding
Merge pull request #951 from batmanjs/save-with-options

allow user to supply which fields to suppress/transmit when saving
corrected a minor spelling error. cleaned up the tests
formatting filters to match project conventions. removing optional argument in precision and fixed. updating tests
changed the name of commafy to numberDelimeter to better represent what it actually does. also added credit to the creator of the regular expressions
changed numberDelimiter to delimitNumber
updating the class binding to not remove existing classes when trying to bind dynamic classes. all associated tests are passing
If a style value that ends in ; is used (i.e. color: #FF0000;) then the parser send's setStyle('colour', '#FF0000') and setStyle('', '').

The second call with a key that is empty, triggers an error in IE8 (and possibly below) when the code hits the @node.style[key] = value code below.
As I assume we should ignore blank keys, I just return false immediately.

Very difficult to test, as it works fine on all modern browsers.

Using storage key if we find it for the location for the urls when using a nested URL.

The problem was identified when using a nested hasOne. The urlNestsUnder method overwrites the url methods for the model, which in turns take priority over the _defaultCollectionUrl method inside the urlForCollection method.
The url method that is re-writted uses a plural resource name, and thus ignores the storageKey set, which (in my understanding) is what should be used.

Added backward compatibility for when storageKey doesn't exist, the legacy pluralisation is utilised.