- Changes
Moya.Error.Underlyingto haveNSErrorinstead ofErrorType. Breaking change
- Makes
convertResponseToResultpublic to make use of this method when dealing with Alamofire directly - Updates to ReactiveCocoa 4.1
- Updates to Result 2.0
- Updates for Swift 2.2 / Xcode 7.3 compatibility.
- Fixed endpoint setup when adding
parametersorheaderswhenparametersorheadersor nil. - Adds StructTarget for using Moya with structs.
- Adds
responsecomputed property toErrortype, which yields a Response object if available. - Added URLEncodedInURL to ParameterEncoding.
- Adds convenience
endpointByAddingmethod. - Remove our own implementation of
ParameterEncodingand make it apublic typealiasofAlamofire.ParameterEncoding.
- Updated to ReactiveCocoa 4.0 final.
- Added formatter parameter to plugin for pretty-printing response data. See #392.
- Compatibility with RxSwift 2.x.
- Compatibility with RxSwift 2.1.x.
- The built-in
DefaultAlamofireManageras parameter's default value instead of the singletonAlamofire.Manager.sharedinstanceis now used when instantiatingReactiveCocoaMoyaProviderandRxMoyaProvideras well.
- Updates to ReactiveCocoa 4 RC 2.
- Breaking Change pass a built-in
DefaultAlamofireManageras parameter's default value instead of passing the singletonAlamofire.Manager.sharedinstancewhen initialize aprovider - Fixes issue that stubbed responses still call the network.
- Updates to RXSwift 2.0.0
- Moves to use Antitypical/Result
- Update to ReactiveCocoa v4.0.0-RC.1
- Fixes cases where underlying network errors were not properly propagated.
- Moves to antitypical Result type
- Updated to RxSwift 2.0.0-beta.4
- Update to ReactiveCocoa v4.0.0-alpha.4
- Breaking Change rename
MoyaTargetprotocol toTargetType - Breaking Change rename
MoyaRequestprotocol toRequestType - Breaking Change rename
Pluginprotocol toPluginType - Removes conversion from
Moya.MethodtoAlamofire.Methodsince it was unused - Changes
NetworkLoggingPlugin's initializer to also take a function that has the same signature asprintto simplify testing - Breaking Change renames
ParameterEncoding'sparameterEncodingmethod totoAlamofireand makes it internal only - Breaking Change
Plugin<Target>is now a protocol and as such no longer sends a typedMoyaProvider. - @swizzlr - Breaking Change The types that were subtypes of
Moyaare now defined at the top level; you should find no compatibility issues since they are still invoked byMoya.X– @swizzlr - Breaking Change
Completionclosure now returns aResultinstead of multiple optional parameters. - Breaking Change
MoyaResponseis nowResponse, and alsofinal. It will be changed to astructin a future release. - @swizzlr - Breaking Change
ReactiveCocoaMoyaProvidercan now be supplied with an optionalstubScheduler– @swizzlr (sponsored by Network Locum) - Breaking Change Introduce
Errortype for use with reactive extensions - @tomburns - Breaking Change Deprecate ReactiveCocoa 2 support
- Adds mapping methods to
MoyaResponse
- Adds tvOS and watchOS support
- Fixes carthage OS X target not having source files
- Makes base OS X target 10.9 instead of 10.10
- Updates to latest ReactiveCocoa alpha. Again.
- Updates to latest ReactiveCocoa alpha.
- Removed extraneous
SignalProducerfrom ReactiveCocoa extension – @JRHeaton - Removed extraneous
deferred()from RxSwift extension - Moved to new RxSwift syntax – @wouterw
- Updated RxSwift to latest beta – @wouterw
- OS X support.
- Fixes Carthage integration problem.
- CancellableTokens can now debug print the requests cURL.
- Plugins now subclasses NSObject for custom subclasses.
- Plugins' methods are now public, allowing custom subclasses to override.
- Updates Alamofire dependency to
~> 3.0
- Changes
mapImage()RxSwift function to useUIImage!instead ofUIImage.
- Makes
parametersonMoyaTargetan optional[String: AnyObject]dictionary. - Makes
parametersandhttpHeaderFieldsonEndpointto be optionals. - Renamed stubbing identifiers: Breaking Change
Moya.StubbedBehaviorrenamed toMoya.StubBehaviorMoya.MoyaStubbedBehaviorrenamed toMoya.StubClosureMoya.NoStubbingBehavior->Moya.NeverStubMoya.ImmediateStubbingBehaviour->Moya.NeverStubMoya.DelayedStubbingBehaviour->Moya.DelayedStub
- Default class functions have been moved to extensions to prevent inadvertent subclassing.
- Renamed other identifiers: Breaking Change
MoyaProvider.MoyaEndpointsClosuretoMoyaProvider.EndpointClosureMoyaProvider.MoyaEndpointResolutiontoMoyaProvider.RequestClosureMoyaProvider.endpointResolvertoMoyaProvider.requestClosureMoyaProvider.stubBehaviortoMoyaProvider.stubClosureMoyaCredentialClosuretoCredentialClosureMoyaProviderinitializer parameter namesMoyaCompletiontoMoya.CompletionDefaultEndpointResolutiontoDefaultRequestMapping
- Renamed
Tgeneric types ofMoyaProviderandEndpointclasses toTarget. - Removed errantly named
DefaultEndpointResolution - Changes the closure to map
Endpoints toNSURLRequests asynchonous. - Removes inflight request tracking for ReactiveCocoa and RxSwift providers. Breaking Change
- Adds support for ReactiveCocoa 4 by moving
ReactiveCocoaMoyaProviderto useSignalProducerinstead ofRACSignal - Renamed
EndpointSampleResponsecases: Breaking ChangeSuccesstoNetworkResponse, now containsNSDatainstead of() -> NSData.ErrortoNetworkError- Additionally,
NetworkErrorno longer has a status code or data associated with it. This represents an error from the underlying iOS network stack, like an inability to connect. See #200 for more details. - Also additionally, removed
Closurecase (see below).
- Changed
Endpointto use asampleResponseClosureinstead of asampleResponse, making all sample responses lazily executed. Breaking Change - New plugin architecture Breaking Change
- This replaces
networkActivityClosurewith a plugin.
- This replaces
- ReactiveCocoa provider no longer replaces errors that contain status codes (an unlikely situation) with its own errors. It passes all errors directly through.
- Renames
tokentotarget(it was usuallytargetanyway, just made it consistent).
- Corrects problem with ignoring the specified Alamofire manager
- Adds HTTP basic auth support.
- Adds data processing functions for use with
RxMoyaProvider
- Adds convenience
endpointByAddingParameterEncodingmethod.
- Adds Moya files as members of RxMoya and ReactiveMoya frameworks.
- Add backward-compatible call from
DefaultEnpointResolutiontoDefaultEndpointResolutiononMoyaProviderclass.DefaultEndpointResolutionis now used internally as the default resolver.DefaultEnpointResolutioncan be removed in a future major release. - Carthage support.
- Add option to pass an
Alamofire.ManagertoMoyaProviderinitializer
- Updates Demo directory's RxSwift version.
- Updates Demo directory's Moya version for
pod trycompatbility.
- Breaking change Combines
MoyaPathandMoyaTargetprotocols. - Breaking change Renames
Moya/Reactivesubspec toMoya/ReactiveCocoa. - Breaking change Removes
stubResponsesfrom initializer; replaced with new stubbing behavior.NoStubbing. Added class methods toMoyaProviderto provide defaults, while allowing users to still change stubbing behaviour on a per-request basis. - Breaking change Redefines types of
DefaultEndpointMappingandDefaultEnpointResolutionclass functions onMoyaProvider. You no longer invoke these functions to return a closure, rather, you reference the functions themselves as closures. - Breaking change Renames
endpointsClosureparameter and property ofMoyaProvidertoendpointClosure. - Breaking change Renames
ReactiveMoyaProvidertoReactiveCocoaMoyaProviderfor consistency. - Fixes problem that the
ReactiveMoyaProviderinitializer 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
- Fixes problem where
RxMoyaProviderwould not respect customized stubbing behaviour (delays).
- Adds support for RxSwift – @alcarvalho
- Breaking change Changes
EndpointSampleResponseto require closures that returnNSData, notNSDatainstances themselves. This prevents sample data from being loaded during the normal, non-unit test app lifecycle. - Breaking change Adds
methodtoMoyaTargetprotocol and removesmethodparameter fromrequest()functions. Targets now specify GET, POST, etc on a per-target level, instead of per-request. - Breaking change Adds
parameterstoMoyaTargetprotocol and removes ability to pass parameters intorequest()functions. Targets now specify the parameters directly on a per-target level, instead of per-request. - Adds a sane default implementation of the
MoyaProviderinitializer'sendpointsClosureparameter.
- Updates to Swift 1.2.
- Adds cancellable requests -@MichaelMcGuire
- Adds network activity closure to provider.
- Updates podspec to refer to
3.0.0-aplha.1of ReactiveCocoa. -@ashfurrow
- 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
- 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
- Implements #46, the code property of the NSError sent through by ReactiveMoyaProvider will now match the failing http status code. -@powerje
- Fixes #48 that modifies Moya to execute completion blocks of stubbed responses immediately, instead of using
dispatch_asyncto 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 vendRACSignalinstances that start the network request when subscribed to. -@ashfurrow
- 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
- Initial release.