3.0

• Support Mantle 2.0. Pull Request #87 (@sodastsai)
• Refine project structure including reorganizing folders, use subspecs, and share common codes
  Pull Request #91 (commits) (@sodastsai, @ryanmaxwell)
• Refine the dependency to PromiseKit. Pull Request #85 (@mxcl)
• Fix Core Data threading issue when saving objects Pull Request #76 (@nunofgs)
• Adding a Wildcard URL Matcher and Fix URL pattern matching for higher level paths Pull Request #94 Pull Request #55 (@brandons, @groomsy)

Summary of 3.0 release

• Support Mantle 2.0
• Use podspec to re-organize features. (Take CoreData and Social support apart from Core)
• Separate CoreData classes (for example, OVCHTTPSessionManager -> OVCManagedHTTPSessionManager)

Migrate from 2.x

1. Mantle 2.x Support

By default, Overcoat 3.x installs Mantle 2.x as dependency.
If you still have to stick with Mantle 1.x, then besides adding Overcoat, you have to specify this explicitly by:

pod 'Mantle', '~> 1.5'

2. Podspec change

The podspec has been changed, so you may have to change your Podfile into:

• if you just use AFNetworking and Mantle but don't use CoreData, you don't have to change anything. (but the version number)

pod 'Overcoat', '~> 3.0'

• if you want to use Overcoat with CoreData

# With Mantle 2.x
pod 'Overcoat/CoreData', '~> 3.0'
# Or with Mantle 1.x
pod 'Overcoat/CoreData/Mantle1', '~> 3.0'

• if you want to use Overcoat with Social request serializer

pod 'Overcoat/Social`, '~> 3.0'

• if you want to use multiple Overcoat subspecs

pod 'Overcoat', :subspecs => ['CoreData', 'Social'], '~> 3.0'

• The support of PromiseKit and ReactiveCocoa are not changed, so you could keep using

pod 'Overcoat/PromiseKit', '~> 3.0'
pod 'Overcoat/ReactiveCocoa', '~> 3.0'

• The support of NSURLSession has been merged into the Core subspec, so you could just use

pod 'Overcoat', '~> 3.0'

3. Classes/Procotols changes

CoreData support of following classes:

• OVCHTTPRequestOperationManager
• OVCHTTPSessionManager
• OVCModelResponseSerializer

has been move to their subclasses:

In most cases, you could just switch your class name from orginial one to CoreData-supported one
if you are using CoreData support.

Also there are two base procotols:

• OVCHTTPManager defines common interfaces of OVCHTTPSessionManager and OVCHTTPRequestOperationManager.
• OVCManagedHTTPManager extends the OVCHTTPManager protocl and defines common interfaces for CoreData support.

• Bug fixes

With kind contributions from @eytanbiala and @stefreak

• Allow customization of Response classes per resource paths.
• Bug fixes

Thanks to @eliasturbay and @ryanmaxwell for their contributions.

Fix PromiseKit version in podspec and specify a default subspec.

Fixes PromiseKit breaking changes!

• New API
• Add NSURLSession based clients
• Add Core Data persistence
• Add Envelop and Error responses
• Add ReactiveCocoa extensions
• Add PromiseKit extensions

Special thanks to @joanromano for contributing the ReactiveCocoa extensions and to everyone that reviewed the pull requests.

• New API
• Add NSURLSession based clients
• Add Core Data persistence
• Add Envelop and Error responses
• Add ReactiveCocoa extensions
• Add PromiseKit extensions

Special thanks to @joanromano for contributing the ReactiveCocoa extensions and to everyone that reviewed the pull requests.

• Fix AFNetworking deprecation warnings
• Replace git submodules with cocoa pods
• Update unit tests to XCTest
• Use appledoc format for documentation

What's New

This version is focused in supporting the new AFNetworking 2.0 architecture. Here's a summary of the changes:

• OVCModelResponseSerializer serializes JSON responses into model objects.
• OVCSocialRequestSerializer serializes requests into ACAccount authenticated requests.
• OVCClient now inherits from AFHTTPRequestOperationManager. The interface remains almost the same.
• OVCRequestOperation has been deprecated.
• OVCSocialClient has been deprecated. Use the new +clientWithBaseURL:account: method in OVCClient instead.

OVCSocialClient properties are now read-only

Both OVCClient and OVCRequestOperation have new interfaces, less cluttered and more consistent with the rest of AFNetworking.