Skip to content

CHANGELOG.md

Latest commit

 

History

History
87 lines (53 loc) · 5.04 KB

CHANGELOG.md

File metadata and controls

87 lines (53 loc) · 5.04 KB
Raw
  • Add backward-compatible call from DefaultEnpointResolution to DefaultEndpointResolution on MoyaProvider class. DefaultEndpointResolution is now used internally as the default resolver. DefaultEnpointResolution can be removed in a future major release.

2.1.0

  • Add option to pass an Alamofire.Manager to MoyaProvider initializer

2.0.2

  • Updates Demo directory's RxSwift version.

2.0.1

  • Updates Demo directory's Moya version for pod try compatbility.

2.0.0

  • Breaking change Combines MoyaPath and MoyaTarget protocols.
  • Breaking change Renames Moya/Reactive subspec to Moya/ReactiveCocoa.
  • Breaking change Removes stubResponses from initializer; replaced with new stubbing behavior .NoStubbing. Added class methods to MoyaProvider to provide defaults, while allowing users to still change stubbing behaviour on a per-request basis.
  • Breaking change Redefines types of DefaultEndpointMapping and DefaultEnpointResolution class functions on MoyaProvider. You no longer invoke these functions to return a closure, rather, you reference the functions themselves as closures.
  • Breaking change Renames endpointsClosure parameter and property of MoyaProvider to endpointClosure.
  • Breaking change Renames ReactiveMoyaProvider to ReactiveCocoaMoyaProvider for consistency.
  • Fixes problem that the ReactiveMoyaProvider initializer would not respect the stubbing behaviour it was passed.
  • Adds official Carthage support – @neonichu
  • Relaxes version dependency on RxSwift - @alcarvalho
  • Fixes possible concurrency bugs with reactive providers - @alcarvalho

1.1.1

  • Fixes problem where RxMoyaProvider would not respect customized stubbing behaviour (delays).

1.1.0

1.0.0

  • Breaking change Changes EndpointSampleResponse to require closures that return NSData, not NSData instances themselves. This prevents sample data from being loaded during the normal, non-unit test app lifecycle.
  • Breaking change Adds method to MoyaTarget protocol and removes method parameter from request() functions. Targets now specify GET, POST, etc on a per-target level, instead of per-request.
  • Breaking change Adds parameters to MoyaTarget protocol and removes ability to pass parameters into request() functions. Targets now specify the parameters directly on a per-target level, instead of per-request.
  • Adds a sane default implementation of the MoyaProvider initializer's endpointsClosure parameter.

0.8.0

  • Updates to Swift 1.2.

0.7.1

0.7.0

  • Adds network activity closure to provider.

0.6.1

  • Updates podspec to refer to 3.0.0-aplha.1 of ReactiveCocoa. -@ashfurrow

0.6

  • First release on CocoaPods trunk.
  • Add data support for stubbed error responses. – @steam
  • Fixes #66, a problem with outdated Alamofire dependency and it's serializer type signature. -@garnett
  • Delete note about ReactiveCocoa installation -@garnett

0.5

  • Fixes #52 to change submodules to use http instead of ssh. -@ashfurrow)
  • Migrate to support Xcode beta 6.1 -@orta)
  • Adds the original NSURLResponse to a MoyaResponse -@orta)
  • Fixes #63, a problem where stale inflight requests were kept around if they error'd down the pipline (discussed here) -@ashfurrow

0.4

  • Implements #46, the code property of the NSError sent through by ReactiveMoyaProvider will now match the failing http status code. -@powerje

0.3

  • Fixes #48 that modifies Moya to execute completion blocks of stubbed responses immediately, instead of using dispatch_async to defer it to the next invocation of the run loop. This is a breaking change. Because of this change, the ReactiveCocoa extensions had to be modified slightly to deduplicate inflight stubbed requests. Reactive providers now vend RACSignal instances that start the network request when subscribed to. -@ashfurrow

0.2

  • Fixes #44 where status codes weren't being pass through to completion blocks. This also modified the behaviour of the ReactiveCocoa extensions significantly but sending MoyaResponse objects instead of just NSData ones. —@ashfurrow

0.1

  • Initial release.