- Pin dependencies to their major versions only, so no specific minor or patch versions are required. #2207 by @BasThomas.
- Added
NetworkLoggerPlugin.defaultandNetworkLoggerPlugin.verboseto conveniently access the default plugins. #2095 by @sunshinejr.
- Breaking Change Changed
Hashable&&Equatableimplementation ofEndpointsince it was returning false positives. #2101 by @sunshinejr. - Breaking Change
MultiPartFormDatais nowHashable. #2101 by @sunshinejr. - Breaking Change
AccessTokenPluginnow usesTargetType, instead ofAuthorizationType, in the closure to determine the token. FullMultiTargetintegration added as well. #2046 by @Coder-ZJQ. Target.sampleDatais now automatically implemented asData()with default protocol extension. #2015 by jdisho.- Breaking Change Minimum version of
RxSwiftis now 6.0. #2120 by @peagasilva. - Moya's Swift minimum version is now Swift 5.2. #2120 by @peagasilva.
- Moya now depends on the latest versions of RxSwift, ReactiveSwift & Alamofire. #2197 by @BasThomas.
- Fixed an issue where when using
trackInflightsoption in certain circumstances would return a cached response for an endpoint that's not really the same. #2101 by @sunshinejr. - Fixed a crash where Combine Publisher would crash when using stubs. #2072 by jshier.
- Fixed Unit Tests and CI. #2187 by OhKanghoon.
- Fixed a race condition that could prevent plugin's
willSend(_:target:)from being fired. #2192 by anton-plebanovich.
- We brought back Combine support! #2024 by @MaxDesiatov.
- Moya's Swift minimum version is now Swift 5.1. #1931 by @BasThomas and @LucianoPAlmeida.
- Breaking Change Minimum version of
Alamofireis now 5.0. #1992 by @sunshinejr. - Breaking Change
MultiTargetnow implementsAccessTokenAuthorizableso that the inner target'sauthorizationTypeis correctly returned to theAccessTokenPluginwhen requested. #1979 by @amaurydavid.
- Breaking Change In
AccessTokenPlugin, the token closure now takes aAuthorizationTypeas parameter andAuthorizationType.nonehas been removed in favor of usingAuthorizationType?. #1969 by @amaurydavid.
- Fixed a data race condition issue and enable TSAN on the test action and CI. #1952 by @LucianoPAlmeida.
- Breaking Change Minimum version of
Alamofireis now 5.0.0-rc.3. #1944 by @sunshinejr.
- Breaking Change Removed Combine extensions for now. Due to problems with weak-linking the framework, it's too difficult to support it with ease using all package managers and also without breaking backwards-compatibility. Probably gonna introduce it once we only support Xcode 11. #1933 by @sunshinejr
- Fixed an issue with displaying cURL-formatted request in
NetworkLoggerPlugin. #1916 by @sunshinejr. - Fixed an issue that wouldn't display stubbed response body in
NetworkLoggerPlugin. #1916 by @sunshinejr. - Fixed an issue where Carthage users using Xcode 11 couldn't install Moya 14. We added weak-linking for the xcodeproj so you might need additional steps for Xcode 10 + Carthage + Moya 14.* users. #1920 by @fredpi and @sunshinejr.
- Fixed an issue that wouldn't persist
URLRequestchanges (created by plugins) when stubbed. #1921 by @sunshinejr. - Fixed an issue with SPM integration - it no longer fetches testing libraries and also doesn't create runtime/Xcode Preview crashes. #1923 by @sunshinejr.
- Breaking Change Minimum version of
Alamofireis now 5.0.0-rc.2. #1912 by @sunshinejr.
- Combine support! #1904 by @sunshinejr.
- Very raw SPM testing support! Thanks to the work on OHHTTPStubs, we can finally start using
swift testagain. #1896 by @sunshinejr.
- Breaking Change Minimum version of
Alamofireis now 5.0.0-rc.1. #1909 by @sunshinejr. - Breaking Change The NetworkLoggerPlugin have been reworked to allow more customization about the logged request's components. #1894 by @amaurydavid.
- Breaking Change Bumped ReactiveSwift version to 6.1.0. This should only affect Carthage users, but you'll probably want to use 6.1.0 in all of your Xcode 11 projects. #1896 by @sunshinejr.
NetworkLoggerPluginnow logs error when available (usingLogOptions.verboseor specyfingerrorResponseBodyin yourLogOptions). #1880 by @amaurydavid.
RequestTypenow hassessionHeaders! These are the headers that are added when the request is added to a session. #1878 by @sunshinejr.
- Breaking Change Minimum target version are now in line with Alamofire 5. iOS: 10.0, tvOS: 10.0, macOS: 10.12, watchOS: 3.0. #1810 by @sunshinejr.
- Breaking Change Minimum version of
Alamofireis now 5.0.0-beta.7. #1810 by @sunshinejr. - Breaking Change Removed
Resultdepndency in favor ofResultintroduced in Swift 5. #1858 by @larryonoff. - Breaking Change Added
TargetTypeparameter in the output ofNetworkLoggerPlugin. #1866 by @hasankose. NetworkLoggerPluginuses the newly addedsessionHeadersand now logs all the headers that the request will produce. #1878 by @sunshinejr.
- Breaking Change Minimum version of
RxSwiftis now 5.0. #1846 by @LucianoPAlmeida. - Breaking Change Minimum version of
ReactiveSwiftis now 6.0. #1849 by @sunshinejr.``
- Fixed a problem where, while using stubbed responses, Moya would generate weird cancellation errors in the console. #1841 by @sunshinejr.
- Breaking Change
.mapImage()extension onSingleandObservablenow returns non-optional image. #1789, #1799 by @bjarkehs and @sunshinejr. - Breaking Change Minimum version of
ReactiveSwiftis now 5.0. #1817 by @larryonoff. - Breaking Change Minimum version of
Resultis now 4.1. #1817 by @larryonoff. - Breaking Change Updated project to Swift 5.0. #1827 by @sunshinejr.
- Updated project to support Xcode 10.2. #1826 by @larsschwegmann.
MoyaErrornow conforms toCustomNSErrorprotocol, makes underlying errors available in its user-info dictionary. #1783 by @dpoggi.
- Fixed
Progressobject on responses that did not specify correctContent-Lengthheader. Now, whenever there is no valid header, the progress will be 0.0 until the completion of the request. Also, thecompletedproperty is nowtrueonly when the response was serialized, we do not rely on progress being 1.0 anymore. #1815 by @sunshinejr.
- Breaking change Removed
validateonTargetType. It was deprecated in Moya 11, usevalidationTypeinstead. #1828 by @sunshinejr.
- Breaking Change Minimum watchOS deployment target for Moya is now 3.0. #1758 by @SD10.
- Fix warnings generated by Xcode 10. Updated project to Swift 4.2 #1740 by @lexorus
- Breaking Change Added
.custom(String)authorization case toAuthorizationTypeinsideAccessTokenPlugin. #1611 by @SeRG1k17.
-
Breaking Change Minimum version of
ReactiveSwiftis now 4.0. #1668 by @sunshinejr. -
Breaking Change Minimum version of
Resultis now 4.0. #1668 by @sunshinejr. -
Breaking Change Changed
Responses filter method parameter to use a genericRangeExpressionthat accepts any range type. #1624 by @LucianoPAlmeida. -
Breaking Change Changed
AccessTokenPlugin's initializer to no longer use an@autoclosurefor thetokenClosureparameter. #1611 by @SeRG1k17.
- Fixed Carthage compatibility by disabling the SwiftLint build phase in release builds. #1619 by @Dschee.
- Fixed Alamofire validation not being performed on
.uploadMultipartrequests. #1591 by @SD10. - Fixed Alamofire validation not being performed on stubbed requests. #1593 by @SD10.
- No changes
- Breaking Change Added a
.requestCustomJSONEncodablecase toTask. #1443 by @evgeny-sureev. - Breaking Change Added
failsOnEmptyDataboolean support for theDecodablemap functions. #1508 by @jeroenbb94.
- Breaking Change Updated minimum version of
ReactiveSwiftto 3.0. #1470 by @larryonoff. - Breaking Change Changed the
validateproperty ofTargetTypeto use newValidationTypeenum representing valid status codes. #1505 by @SD10, @amaurydavid.
- Fixed a bug where modifying
.uploadMultipart,.uploadCompositeMultipart,.uploadFile,.downloadDestination, and.downloadParameterstasks through anendpointClosurehas no effect on the final request. #1550 by @SD10, @sunshinejr. - Fixed a bug where
URLEncoding.httpBodywasn't allowed asbodyEncodinginTask.requestCompositeParameters(). #1557 by @sunshinejr.
- Fixed a bug that
Decodablemapping to object other than Array and Dictionary in a key path cause crash. #1405 by @ufosky. - Fixed a bug with missing Content-Type header when using
.requestJSONEncodable#1410 by @Vict0rS. - Fixed linker settings, enabling RxMoya and ReactiveMoya to be used in app extensions #1417 by @spookyvision.
- Fixed carthage OS X not targeting 10.10 #1444 by @lucas34.
- Breaking Change Added a
.parameterEncodingcase toMoyaError. #1248 by @SD10. - Breaking Change Added an
.objectMappingcase toMoyaError. #1335 by @devxoul. - Breaking Change Added an
.encodableMappingcase toMoyaError. #1349 by @LeLuckyVint, @afonsograca and @sunshinejr. - Breaking Change Added a
.requestJSONEncodablecase toTask. #1349 by @LeLuckyVint, @afonsograca and @sunshinejr. - Added a
Decodableobject mapping methods toMoya.Response. #1335 by @devxoul.
- Breaking Change Changed
Endpoint.initso it doesn't have any default arguments (removing default argument.getformethodparameter andnilforhttpHeaderFieldsparameter). #1289 by @sunshinejr. - Breaking Change Changed
NetworkActivityPluginso itsnetworkActivityClosurehas nowtarget: TargetTypeargument in addition tochange: NetworkActivityChangeType. #1290 by @sunshinejr. - Breaking Change Changed
Endpoint'surlRequestproperty tourlRequest()a throwing method. #1248 by @SD10.
- Removed default value for task from
Endpointinitializer
- Breaking Change Replaced
parameters¶meterEncodinginTargetTypewith extendedTaskcases. - Breaking Change Flattened
UploadTypeandDownloadTypeintoTaskcases. - Breaking Change Replaced
shouldAuthorize: BoolinAccessTokenAuthorizablewithauthorizationType: AuthorizationType. - Breaking Change Replaced
tokeninAccessTokenPluginwithtokenClosure. - Breaking Change
TargetTypesno longer receive theAuthorization: Bearer <token>header by default when usingAccessTokenPlugin.
- Added Swift 4.0 support for Moya core (without RxSwift/ReactiveSwift extensions for now).
- Added all the
filter/mapoperators that were available forObservable<Response>toSingle<Response>as well. - Added
AuthorizationTypetoAccessTokenAuthorizablerepresenting request headers of.none,.basic, and.bearer. - Added tests for
Single<Response>operators. - Added
Progressobject into the response when calling progress callback on completion. - Added tests for creating
URLRequestfromTask.
- Fixed a bug where you weren't notified on progress callback for data request.
- Breaking Change Added support to get the response (if any) from
MoyaError. - Breaking Change Added
headerstoTargetType. - Breaking Change Updated
RxMoyaProvider.requestto return aSingle<Request>. - Breaking Change Updated
Moya.Response'sresponseto use anHTTPURLResponseinstead of aURLResponse. - Breaking Change Renamed all occurrences of
queuetocallbackQueue. - Breaking Change Deprecated
ReactiveSwiftMoyaProviderandRxSwiftMoyaProvider. UseMoyaProviderwith reactive properties now:provider.reactive._,provider.rx._. In case you were subclassing reactive providers, please take a look at this PR from Eidolon. It covers migration from subclassing given providers, to usage by composition. - Breaking Change Removed parameter name in
requestWithProgressforReactiveSwiftMoyaProvider. - Breaking Change Removed deprecated in Moya 8.0.0:
Moya.Error,endpointByAddingParameters(parameters:),endpointByAddingHttpHeaderFields(httpHeaderFields:),endpointByAddingParameterEncoding(newParameterEncoding:),endpointByAdding(parameters:httpHeaderFields:parameterEncoding),StructTarget,filterStatusCodes(range:),filterStatusCode(code:),willSendRequest(request:target:),didReceiveResponse(result:target:),ReactiveCocoaMoyaProvider,ReactiveSwiftMoyaProvider.request(token:).
- Added optional callback queue parameter to reactive providers.
- Added public
URL(target:)initializator that creates url fromTargetType. - Added an optional
requestDataFormatterinNetworkLoggerPluginto allow the client to interact with the request data before logging it.
-
Fixed a bug where you would have two response events in
requestWithProgressmethod onReactiveSwiftmodule. -
Enabled the "Allow app extension API only" flag.
-
Updated minimum version of
RxSwiftto3.3. -
Updated minimum version of
ReactiveSwiftto 2.0.
- Fixed a bug where you would have two response events in
requestWithProgressmethod on RxMoya module.
- Bumped minimum version of ReactiveSwift to 1.1.
- Changed use of deprecated
DateSchedulerProtocoltoDateScheduler. - Move project to using a single target for all platforms.
- Changed default endpoint creation to only append
pathtobaseURLwhenpathis not empty.
- Fixed
reversedPrintarguments for output. - Fixed memory leak when request with stub.
- Changed
Moya.ErrortoMoyaErrorinMoyaAvailablityfor Swift 3.1 compatibility.
- Changed dependency pinning to rely only on major versions.
- Fixed an issue where
RxMoyaProvidernever sendsnextor errors if it's disposed before a subscription is made.
- Breaking Change Renamed
Moya.ErrortoMoyaError. - Breaking Change Renamed
verbosein the NetworkLoggerPlugin toisVerbose. - Breaking Change
TargetTypenow specifies itsParameterEncoding. - Breaking Change Removed unused
Moya.Error.data. - Breaking Change Renamed
adding(newHttpHeaderFields:)toadding(newHTTPHeaderFields:).
- Supported the Swift package manager
- Added
AccessTokenPluginfor easier authorization. - Added
AccessTokenAuthorizableprotocol for optionally controlling the authorization behavior ofTargetTypes when usingAccessTokenPlugin. - Added availability tags for renamed functions included in the Swift 3 migration.
Moya.Errornow conforms toLocalizedErrorprotocol.- Added documentation for
TargetTypeand associated data structures. - Re-add
MultiTargetto project.
- Adopted an SPM-compatible project structure.
- Moved tests to Moya.xcodeproj.
- Breaking Change Renamed
ReactiveCocoaMoyaProvidertoReactiveSwiftMoyaProvider. - Breaking Change Renamed
PluginTypefunctions to comply with Swift 3 design guideline:willSendRequestrenamed towillSend.didReceiveResponserenamed todidReceive.
- Breaking Change Renamed
filterStatusCodes(:)tofilter(statusCodes:)(andfilterStatusCode(:)tofilter(statusCode:)). - Breaking Change Renamed
request(token:)to simplyrequest(:_)(ReactiveSwift). - Breaking Change Renamed
notifyPluginsOfImpendingStub(request:)tonotifyPluginsOfImpendingStub(for:). - Renamed the
ReactiveCocoasubspec toReactiveSwift. PluginTypecan now modify requests and responses throughprepareandprocess
- Breaking Change Renamed
cancelledin theCancellableprotocol toisCancelled. - Breaking Change Renamed
URLinEndpointtourl. - Breaking Change Renamed
StructTargettoMultiTarget. - Demo project has been updated with new DemoMultiTarget target, new project structure and more.
- Readded support for iOS 8 and macOS 10.10.
- Added validate option in
TargetType, to allow enabling Alamofire automatic validation on requests. - Added
mapString(atKeyPath:)toResponse,SignalProducerProtocol, andObservableType
- Breaking Change Made some
class funcs mimicking enum cases lowercased. - Updates for RxSwift 3.0 final release.
- Added default empty implementation for
willSendRequestanddidReceiveResponseinPluginType. - Use
String(data:encoding:)instead ofNSString(data:encoding:)while convertingDatatoString.
- Breaking Change Throw dedicated
Error.jsonMappingwhenmapJSONfails to parse JSON. - Breaking Change Renamed
endpointByAddingHTTPHeaderstoadding(newHttpHeaderFields:). - Breaking Change Renamed
endpointByAddingParameterstoadding(newParameters:). - Breaking Change Renamed
endpointByAddingParameterEncodingtoadding(newParameterEncoding:). - Breaking Change Renamed
endpointByAdding(parameters:httpHeaderFields:parameterEncoding)toadding(parameters:httpHeaderFields:parameterEncoding). - Breaking Change Changed HTTP verbs enum to lowercase.
urlRequestproperty ofEndpointis now truly optional. The request will fail if theurlRequestturns out to be nil and arequestMappingerror will be returned together with the problematic url.- Breaking Change Made RxMoya & ReactiveMoya frameworks dependant on Moya framework, making them slimmer and not re-including Moya source in the Reactive extensions. (PR)
- Removed the unused
StreamRequesttypealias that was causing watchOS failures.
- Fixes download requests never calling the completion block.
- Added a new internal Requestable protocol.
- Added a new case to
SampleResponseClosurewhich allows mocking of the wholeURLResponse. - Added a test for new
SampleResponseClosurecase.
- Breaking Change Transition from ReactiveCocoa to ReactiveSwift. (PR)
- Breaking Change Support for
Swift 3in favor ofSwift 2.x. - Breaking Change
fileNameandmimeTypeare now optional properties on a MultipartFormData object. - Correct Alamofire
appendBodyPartmethod id called in MultipartFormData. - Breaking Change Removes
multipartBodyfrom TargetType protocol and adds ataskinstead. - Breaking Change Successful Response instances that have no data with them are now being converted to
.SuccessResults.
- Adds Download and Upload Task type support to Moya.
- Added
supportsMultipartto theMethodtype, which helps determine whether to usemultipart/form-dataencoding. - Added
PATCHandCONNECTto theMethodcases which support multipart encoding. - Added
requestforResponse.
- Corrects SwiftLint warnings.
- Separates
Moya.swiftinto multiple files. - Updated
mapJSONAPI to include an optional named parameterfailsOnEmptyData:that when overridden returns an emptyNSNull()result instead of throwing an error when the response data is empty.
- Fixes bug for MultipartFormData constructor in Swift 2.3 where fields and files were given a mimetype, forcing them both to be added to the 'files' section.
- Multipart form constructor contains optional Strings
- Carthage support for Swift 2.3.
- Swift 2.3 support.
- Identical to 7.0.0, see #594 for an explanation.
- Breaking Change Drops support for
RACSignal. - Breaking Change Changes
Moya.Error.Underlyingto haveNSErrorinstead ofErrorType. - Breaking Change Implements inflights tracking by adding
trackInflights = trueto your provider. - Breaking Change Changes
MoyaProvider.RequestClosureto haveResult<NSURLRequest, Moya.Error> -> Voidinstead ofNSURLRequest -> Voidas adoneclosure parameter. - Breaking Change New community guidelines.
- New multipart file upload.
- New cURL-based logging plugin.
- Moves from OSSpinLock to
dispatch_semaphorto avoid deadlocks.
- Integrates Danger into the repo.
- Fixes a xcodeproj referencing bug introduced by the new cURL-based logging plugin.
- Calls completion even when cancellable token is canceled
- Added
queueparameter torequestandsendRequest. This open up option to use other queue instead of main queue for response callback.
- 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
- Moves to antitypical Result type
- Fixes cases where underlying network errors were not properly propagated.
- 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.ImmediatelyStubMoya.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
- 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).
- Adds support for ReactiveCocoa 4 by moving
ReactiveCocoaMoyaProviderto useSignalProducerinstead ofRACSignal
- 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 behavior 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. - Relaxes version dependency on RxSwift - @alcarvalho
- Adds official Carthage support – @neonichu
- Fixes problem that the
ReactiveMoyaProviderinitializer would not respect the stubbing behavior it was passed. - Fixes possible concurrency bugs with reactive providers - @alcarvalho
- Fixes problem where
RxMoyaProviderwould not respect customized stubbing behavior (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)
- Fixes #63, a problem where stale inflight requests were kept around if they error'd down the pipline (discussed here) -@ashfurrow
- Adds the original NSURLResponse to a MoyaResponse -@orta)
- Migrate to support Xcode beta 6.1 -@orta)
- 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 passed through to completion blocks. This also modified the behavior of the ReactiveCocoa extensions significantly but sending MoyaResponse objects instead of just NSData ones. —@ashfurrow
- Initial release.