Releases: ishkawa/APIKit Releases · ishkawa/APIKit
5.4.0 02 Oct 07:09
Compare Sorry, something went wrong.
No results found Fix deprecated class keyword #297 Added default implementation of response(from:urlResponse:) when Response is Void #304 Drop support for swift 5.3 and below #303 Support Swift Concurrency #306 5.3.0 01 Jan 03:52
Compare Sorry, something went wrong.
No results found Fix Demo.playground could not be run #293 Change iOS deployment target for Xcode 12 #286 The minimum supported version of iOS is now iOS 9 or later. Thanks @noppefoxwolf for contributing!
5.2.0 25 Feb 04:30
Compare Sorry, something went wrong.
No results found ExpressibleByDictionaryLiteral for JSONBodyParameters #275 Add support for Combine.framework#285 Create a Publisher using Session.shared.sessionTaskPublisher(for:). Fix PBXGroup reference at the project.pbxproj file #287 Thanks @417-72KI and @keisukeYamagishi for contributing!
5.1.0 28 Dec 07:24
Compare Sorry, something went wrong.
No results found Remove to link Result.framework from README.md #274 Fix typo #276 [Swift 5.1] Enable Module Stability #278 Thanks @jumperson and @onevcat for contributing!
5.0.0 17 Apr 11:55
Compare Sorry, something went wrong.
No results found Update to Xcode 10.2 and Swift 5 #268 Thanks @chn-lyzhi for contributing!
4.1.0 06 Apr 00:53
Compare Sorry, something went wrong.
No results found Support Xcode 10 and Swift 4.2 #265 4.0.0 25 Jul 18:11
Compare Sorry, something went wrong.
No results found Update Result dependency to 4.0. Minor update for Xcode 9.3 and Swift 4.1 support. Thanks @ikesyo and @KyoheiG3 for contributing!
3.2.0 24 Dec 14:41
Compare Sorry, something went wrong.
No results found 4.0.0 beta 1 23 Jul 16:12
Compare Sorry, something went wrong.
No results found Add progressHandler parameter to sendRequest(_:) method. Introduce Request.DataParser associated type to express various data format such as JSON, URL query and Protobuf. Introduce QueryParameters protocol for custom URL query parsers. 3.1.2 20 Dec 00:56
Compare Sorry, something went wrong.
No results found Expose CallbackQueue.execute() for customization. #221 Thanks @yshrkt for contributing!