Changelog History
Page 1
-
v5.0.0 Changes
May 22, 2020Yes 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.
-
v4.2.0
March 19, 2019 -
v4.1.2 Changes
January 24, 2017- ๐ [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.
- ๐ [FIXED]: Now using
-
v4.1.1 Changes
December 05, 2016- ๐ [FIXED]: Fixed compilation when building via Swift Package Manager
-
v4.1.0 Changes
November 05, 2016- ๐ [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)
-
v4.0.0 Changes
October 13, 2016๐ 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!
-
v3.1.0 Changes
July 29, 2016๐ 3.1 adds support for decoding
UInt
andUInt64
types.UInt
can only be decodedJSON.Number
instances, andUInt64
can be decoded fromJSON.Number
as well asJSON.String
. This follows the patterns already set up byInt
andInt64
.Thanks to @gcox for this addition!
-
v3.0.3 Changes
July 22, 2016๐ 3.0.3 adds improved support for Xcode 8 by slightly modifying the xml in ways that it suggests (Thanks @ikesyo!)
-
v3.0.2 Changes
July 20, 2016๐ 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.
-
v3.0.1 Changes
April 08, 2016Argo 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
or0
instead oftrue
orfalse
..To address this, we've re-added the capability of Argo to recognize
Bool
values represented in the JSON as numbers.