- Breaking Change pass a built-in
DefaultAlamofireManager
as parameter's default value instead of passing the singletonAlamofire.Manager.sharedinstance
when 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
MoyaTarget
protocol toTargetType
- Breaking Change rename
MoyaRequest
protocol toRequestType
- Breaking Change rename
Plugin
protocol toPluginType
- Removes conversion from
Moya.Method
toAlamofire.Method
since it was unused - Changes
NetworkLoggingPlugin
's initializer to also take a function that has the same signature asprint
to simplify testing - Breaking Change renames
ParameterEncoding
'sparameterEncoding
method totoAlamofire
and 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
Moya
are now defined at the top level; you should find no compatibility issues since they are still invoked byMoya.X
– @swizzlr - Breaking Change
Completion
closure now returns aResult
instead of multiple optional parameters. - Breaking Change
MoyaResponse
is nowResponse
, and alsofinal
. It will be changed to astruct
in a future release. - @swizzlr - Breaking Change
ReactiveCocoaMoyaProvider
can now be supplied with an optionalstubScheduler
– @swizzlr (sponsored by Network Locum) - Breaking Change Introduce
Error
type 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
SignalProducer
from 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
parameters
onMoyaTarget
an optional[String: AnyObject]
dictionary. - Makes
parameters
andhttpHeaderFields
onEndpoint
to be optionals. - Renamed stubbing identifiers: Breaking Change
Moya.StubbedBehavior
renamed toMoya.StubBehavior
Moya.MoyaStubbedBehavior
renamed toMoya.StubClosure
Moya.NoStubbingBehavior
->Moya.NeverStub
Moya.ImmediateStubbingBehaviour
->Moya.NeverStub
Moya.DelayedStubbingBehaviour
->Moya.DelayedStub
- Default class functions have been moved to extensions to prevent inadvertent subclassing.
- Renamed other identifiers: Breaking Change
MoyaProvider.MoyaEndpointsClosure
toMoyaProvider.EndpointClosure
MoyaProvider.MoyaEndpointResolution
toMoyaProvider.RequestClosure
MoyaProvider.endpointResolver
toMoyaProvider.requestClosure
MoyaProvider.stubBehavior
toMoyaProvider.stubClosure
MoyaCredentialClosure
toCredentialClosure
MoyaProvider
initializer parameter namesMoyaCompletion
toMoya.Completion
DefaultEndpointResolution
toDefaultRequestMapping
- Renamed
T
generic types ofMoyaProvider
andEndpoint
classes toTarget
. - Removed errantly named
DefaultEndpointResolution
- Changes the closure to map
Endpoint
s toNSURLRequest
s asynchonous. - Removes inflight request tracking for ReactiveCocoa and RxSwift providers. Breaking Change
- Adds support for ReactiveCocoa 4 by moving
ReactiveCocoaMoyaProvider
to useSignalProducer
instead ofRACSignal
- Renamed
EndpointSampleResponse
cases: Breaking ChangeSuccess
toNetworkResponse
, now containsNSData
instead of() -> NSData
.Error
toNetworkError
- Additionally,
NetworkError
no 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
Closure
case (see below).
- Changed
Endpoint
to use asampleResponseClosure
instead of asampleResponse
, making all sample responses lazily executed. Breaking Change - New plugin architecture Breaking Change
- This replaces
networkActivityClosure
with 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
token
totarget
(it was usuallytarget
anyway, 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
endpointByAddingParameterEncoding
method.
- Adds Moya files as members of RxMoya and ReactiveMoya frameworks.
- Add backward-compatible call from
DefaultEnpointResolution
toDefaultEndpointResolution
onMoyaProvider
class.DefaultEndpointResolution
is now used internally as the default resolver.DefaultEnpointResolution
can be removed in a future major release. - Carthage support.
- Add option to pass an
Alamofire.Manager
toMoyaProvider
initializer
- Updates Demo directory's RxSwift version.
- Updates Demo directory's Moya version for
pod try
compatbility.
- Breaking change Combines
MoyaPath
andMoyaTarget
protocols. - Breaking change Renames
Moya/Reactive
subspec toMoya/ReactiveCocoa
. - Breaking change Removes
stubResponses
from initializer; replaced with new stubbing behavior.NoStubbing
. Added class methods toMoyaProvider
to provide defaults, while allowing users to still change stubbing behaviour on a per-request basis. - Breaking change Redefines types of
DefaultEndpointMapping
andDefaultEnpointResolution
class functions onMoyaProvider
. 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 ofMoyaProvider
toendpointClosure
. - Breaking change Renames
ReactiveMoyaProvider
toReactiveCocoaMoyaProvider
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
- Fixes problem where
RxMoyaProvider
would not respect customized stubbing behaviour (delays).
- Adds support for RxSwift – @alcarvalho
- Breaking change Changes
EndpointSampleResponse
to require closures that returnNSData
, notNSData
instances themselves. This prevents sample data from being loaded during the normal, non-unit test app lifecycle. - Breaking change Adds
method
toMoyaTarget
protocol and removesmethod
parameter fromrequest()
functions. Targets now specify GET, POST, etc on a per-target level, instead of per-request. - Breaking change Adds
parameters
toMoyaTarget
protocol 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
MoyaProvider
initializer'sendpointsClosure
parameter.
- Updates to Swift 1.2.
- Adds cancellable requests -@MichaelMcGuire
- Adds network activity closure to provider.
- Updates podspec to refer to
3.0.0-aplha.1
of 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_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 vendRACSignal
instances 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.