All Versions
49
Latest Version
Avg Release Cycle
60 days
Latest Release
1284 days ago
Changelog History
Page 2
Changelog History
Page 2
-
v5.0.0-beta.3 Changes
May 17, 2019โ Added
- Ability to traverse json to any level when using SwiftyJSONDecodable.
๐ Changed
- ๐ Improved response serializer behavior for cases where requests were stubbed using URLProtocol.
- TRON 5 requires RxSwift 5 and SwiftyJSON 5
- 0๏ธโฃ
Core
is now a default subspec for CocoaPods installation method. To use SwiftyJSON, add following to Podfile:
pod 'TRON/SwiftyJSON'
-
v5.0.0-beta.2 Changes
April 06, 2019๐ Changed
ErrorSerializable
protocol changed to have non-optional initializer and to not acceptserializedObject
. It no longer can be used for additional object validation, but behavior should be more predictable and straightforward -ErrorSerializable
should only be created if somebody (URL loading system, Alamofire or Model serialization) actually reported error.codable
is now a lazy stored property instead of computed property.CodableSerializer
API has been made open to allow easy customization in subclasses.- ๐ง
NetworkLoggerPlugin
now has a constructor that allows to easily configure it's behavior.
๐ฅ Breaking
- Properties that worked with
Alamofire.SessionManager
have been renamed tosession
to be in line withAlamofire
renaming ofSessionManager
toSession
.
โ Removed
- 0๏ธโฃ
TRON.defaultAlamofireManager()
method. TRON initializer now usesAlamofire.Session.default
as a replacement. TRON.processingQueue
property
-
v5.0.0-beta.1 Changes
March 12, 2019TRON now requires:
- Xcode 10
- Swift 4 and higher
- iOS/tvOS 10 and higher
- watchOS 3 and higher
- ๐ macOS 10.12 and higher
โ Added
- ๐ Complete documentation
TRONDataResponseSerializer
andTRONDownloadResponseSerializer
structs to encapsulate serialization of responses using closure.- โ
All test suite now uses
StubbingURLProtocol
to stop tests from sending network requests. Closes #21. - โ Additional
JSONDecodable
conformances have been added for arithmetic types such asInt8...Int64
,UInt8...64
.
โ Removed
EmptyResponse
type was replaced withAlamofire.Empty
struct to not interfere withAlamofire.EmptyResponse
protocol.TRON.stubbingShouldBeSuccessful
property since now each stub directly defines it's behavior instead of global setting- Conditional conformance of
Array
toJSONDecodable
- Convenience download methods on
CodableSerializer
andJSONDecodableSerializer
AuthorizationRequirement
enum. Please useAlamofire.RequestAdapter
andSession.adapter
property to adapt request, when additional headers are needed.HeaderBuildable
protocol andHeaderBuilder
types. Please useBaseRequest.headers
property of typeAlamofire.HTTPHeaders
directly.ErrorHandlingDataResponseSerializerProtocol
andErrorHandlingDownloadResponseSerializer
protocol. Now,ErrorModel
on all requests conforms toErrorSerializable
protocol, that contains initializer that allows to create it directly.- ๐
CodableDownloadParser
andJSONDecodableDownloadParser
, replacement classDownloadSerializer
has been introduced, it allows to create a data model by implementingDownloadResponseSerializerProtocol
UploadAPIRequest.performMultipart
method, because multipart upload is no longer a special case inAlamofire 5
, please useUploadAPIRequest.perform
instead.
๐ฅ Breaking
- 0๏ธโฃ
headers
property ofBaseRequest
now containsHTTPHeaders
type instead of[String: String]
. Please note that along withHeaderBuilder
removal TRON no longer sends 'Accept':'application/json' header by default. APIError
is changed to be able to acceptSerializedObject
and is now a class with nullable initializer. Also,DownloadAPIError
type has been introduced for download errors, that do not haveData
in them, but havefileURL
instead.- ๐
Plugin
methods that previously acceptedAPIError<ErrorModel>
now acceptErrorModel
directly. AddeddidSuccessfullyParseDownloadResponse
anddidReceiveDownloadResponse
methods. - ๐ All concrete implementations of
DataResponseSerializerProtocol
such asCodableParser
andJSONDecodableParser
now have only one generic argument -Model
and are only parsing model type. - ๐
JSONDecodableParser
andCodableParser
now have only one generic argument -Model
, sinceErrorModel
is now moved toErrorSerializable
protocol, that does not depend on any particular serializer. - ๐
APIStub
has been rewritten from scratch to allow injecting only results of network request(URLRequest
,HTTPURLResponse
,Data
,Error
andfileURL
) as opposed to actualModel
anderrorModel
as well as definition of successful/unsuccessful requests.APIStub
now is been attached toAlamofire.Request
when stubbing for this particular request has been enabled. Rewrite also allows plugin callbacks to be called more consistently for both stubbed and unstubbed cases. - ๐
rxMultipartResult
method onUploadRequest
method was removed sinceUploadRequest
for multipart requests in Alamofire 5 is now synchronous and now does not require special handling. You can now callrxResult
replacement method instead.
-
v4.2.2 Changes
April 08, 2019- Swift 4.2 version is now specified in podspec for users of CocoaPods 1.6.x.
๐ This is the last release that supports Xcode 9 and Swift 3.
-
v4.2.1 Changes
May 03, 2018๐ Fixed
- ๐
UploadAPIRequest
now callsdidReceiveDataResponse
plugin methods when sending multipart-form requests.
- ๐
-
v4.2.0 Changes
April 12, 2018- ๐ Implemented
JSONDecodable
support for Arrays, whose Element is JSONDecodable. Requires Swift 4.1 to work.
- ๐ Implemented
-
v4.1.2 Changes
February 27, 2018- ๐ Improved output of
NetworkLoggerPlugin
, which now includes status codes, HTTP body contents, and some emojis ๐
- ๐ Improved output of
-
v4.1.1 Changes
February 27, 2018- ๐ Allow
EmptyResponse
to be used with CodableParser when network response does not contain valid JSON.
- ๐ Allow
-
v4.1.0 Changes
- ๐ Deprecate TRON level headerBuilder in favor of Alamofire.requestAdapter.
- ๐ Loosen CodableParser generic constraints to be able to work with
Decodable
protocol instead ofCodable
.
-
v4.0.0 Changes
- Compiled with Xcode 9.1 / Swift 4.0.2