All Versions
11
Latest Version
4.0
Avg Release Cycle
39 days
Latest Release
-

Changelog History
Page 1

  • v4.0 Changes

    👀 See https://github.com/Overcoat/Overcoat/issues/113

    Migrate from 3.x

    ⬆️ 1. Support of Mantle 1.x has been dropped. Upgrade your models to Mantle 2.x before migrating to Overcoat 4.0. ⬆️ 2. Overcoat 4.x only works with AFNetworking 3.x, so you have to upgrade your networking manager to 3.x too. 👍 3. Support of NSURLConnection has been dropped since AFNetwokring 3.x doesn't support it either.

    1. Overcoat 4.x is able to be integrated via Carthage. ✅ 5. Support to ReactiveCocoa 3.x/4.x has been tested. The podspec also accept those versions. 👀 6. +[OVCHTTPSessionManager responseClass] has been deprecated. Use +[OVCHTTPSessionManager responseClassesByResourcePath] instead. See default implementation of OVCHTTPSessionManager for migration example. There would be a warning message shown via NSLog for ths. 👀 7. +[OVCHTTPSessionManager errorModelClass] has been deprecated. Use +[OVCHTTPSessionManager errorModelClassesByResourcePath] instead. See TestSessionManager in OVCHTTPSessionManagerTests.m for migration example. There would be a warning message shown via NSLog for ths.
    2. A new property named rawResult has been added into OVCResponse. It's the raw JSON object/array returned from remote server.
    3. OVCURLMatcher accepts not only classes but also blocks for extra matching methods. (Like http request method and response status code) 👍 10. All methods in PromiseKit support has added pmk_ as prefix.
  • v4.0.0-beta.2

    March 05, 2016
  • v4.0.0-beta.1

    December 22, 2015
  • v3.2.2 Changes

    November 06, 2015
    • Sort URL matchers. So while finding matched response class, it would find exact type first. (before *, **, and #). Issue #112 Commit 28aa171 (@sodastsai)
  • v3.2.1 Changes

    October 29, 2015
  • v3.2 Changes

  • v3.1.1 Changes

    September 30, 2015
    • 👉 Make sure the NSURLSessionDataTask isn't suspended. Pull Request #102 (@zinthemoney)
    • Add pod_target_xcconfig settings to make Overcoat able to build while using as a dependency of another pod package. Issue #99 (@NorbertSzydlowski)
  • v3.1 Changes

    • Annotate nullability and lighweight generics of Objective-C Issue #90 (@sodastsai)
    • 🔄 Change podspec to drop support of iOS 6.0 and OS X 10.8. (so now we support iOS 7.0+ and OS X 10.9+) (@sodastsai)
  • v3.0 Changes

    • 👌 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) ruby pod 'Overcoat', '~> 3.0'
    • if you want to use Overcoat with CoreData ```ruby
  • v2.1.1 Changes

    December 18, 2014
    • 🐛 Bug fixes

    With kind contributions from @eytanbiala and @stefreak