CARVIEW |
Navigation Menu
-
-
Notifications
You must be signed in to change notification settings - Fork 194
Releases: thoughtbot/Argo
5.0: Swift Compatibility
Compare
Yes I did get tired of my lazy naming scheme.
5.0 adds explicit support for Swift 5 across all dependency management solutions. There are no other user-facing changes.
Assets 2
4.2: four point two
4.1.2: The Iteration Generation
Compare
- [FIXED]: Now using
Iterator
instead ofGenerator
in our definition ofdecode
forCollection
s. This was renamed in Swift 3.0, and honestly I'm not positive how this was compiling the way it was.
Assets 2
4.1.1: An Actual Useable Library
Compare
- [FIXED]: Fixed compilation when building via Swift Package Manager
Assets 2
4.1: Optional Packages
Compare
- [NEW]: Swift Package Manager Support (Gordon Fontenot)
- [NEW]: Re-introduced
Decoded.optional
with better, simplified behavior (Tony DiPasquale) - [FIXED]: Use
NSNumber
transformation properties instead of casting to decode number values. This now prevents a crash that could occur with Swift 3.0.1 (Gordon Fontenot)
Assets 2
4.0.0: Swift 3 and Multi-Error Debugging
Compare
Official Swift 3.0 release!
- [NEW]: Now you can see all the decoding failures at once! Thanks @klaaspieter
- [Bug Fix]: Optional decoding now behaves as expected. Thanks @pteasima for finding this.
Thanks @gfontenot, @alexwlchan, @mbrandonw, @gcox, and @klaaspieter for all the changes that went into this release!
Assets 2
3.1: unsigned unmastered.
Compare
3.1 adds support for decoding UInt
and UInt64
types. UInt
can only be decoded JSON.Number
instances, and UInt64
can be decoded from JSON.Number
as well as JSON.String
. This follows the patterns already set up by Int
and Int64
.
Thanks to @gcox for this addition!
Assets 2
3.0.3: Now With Different XML
3.0.2: Xcode optimizations
Compare
This release is a back-port of our support for enabling whole module optimization (currently supported on master, but unreleased), as well as support for Xcode 8 using Swift 2.3.
Assets 2
3.0.1: NumberWang
Compare
Argo 3.0 changed the way Booleans were decoded and in doing so, accidentally broke JSON parsing for APIs that didn't quite follow the JSON spec. Specifically, @jshier noted that it's moderately common for APIs to return 1
or 0
instead of true
or false
..
To address this, we've re-added the capability of Argo to recognize Bool
values represented in the JSON as numbers.