Deprecate legacy implementations of date formatter support in favor of value transformers
Change implementation such that each mapping begins with a copy of the default value transformer instead of directly returning a reference to it
Do not attempt to set a property value if the value transformer fails the transformation
Ensure that `preferredDateFormatter` legacy support only returns `NSFormatter` objects
Bail out during parsing of ISO-8601 date strings if we encounter a '/' character as the parser does not support time intervals and they cause invalid parsing
If a time zone cannot be extracted from the ISO-8601 date string then fall back to the default timezone of the date formatter
Migrate ISO-8601 date formatter to the beginning of the value transformer stack
Eliminate unnecessary `RKSetValueForObject` function
Migrate ISO-8601 date formatter to the beginning of the value transformer stack
Introduce `keyOfDictionaryValueTransformer`
Eliminate dependence on deprecated `preferredDateFormatter` in `RKObjectParameterization`
Add `ONLY_ACTIVE_ARCH=NO` to Rake test execution to make Travis happy
Remove trace logging from mapping tests
Add deprecation warnings and comments for legacy date formatting API's
Guard against potential crash in `preferredDateFormatter` in the event there are not any default date formatters
Collapse multiple returns in `preferredDateFormatter`
Capitalize global static variables for default value transformer
Remove trailing slashes from poor copy/paste of the macro implementation
Raise an exception if you invoke `compoundValueTransformerWithValueTransformers:` with a `nil` argument
Revert scheme change