Releases: Anviking/Decodable
Releases · Anviking/Decodable
0.6.0: Swift 4
This release contains no other changes than updated project settings to target Swift 4.
Coming from earlier versions you will be faced with errors like 'Decodable' is ambiguous for type lookup in this context
. Unfortunately you have to use the following import-syntax to get around it:
import protocol Decodable.Decodable
where you can also import other structs and enums as required.
v0.5.1
v0.5: Any
v0.4.4: The Remnant
- Project settings upgraded to support Xcode 8 with legacy Swift 2.3 support.
Note: Unsure if this works with Xcode 7 or if you explicitly have to target v0.4.3
. And if you've clicked on the releases page and wonder where the Swift 3 support is, it's on the master branch. Stable releases are coming.
v0.4.3: Last of its kind
v0.4.2: Code Generation
v0.4.1
v0.4: Age of Errors
- Added NSValueCastable protocol for decoding
[U]Int8
,[U]Int16
… - (Re)added
=>?
, this time only for accepting TypeMismatches. - Errors are now structs conforming to
DecodingError
v0.3.4
- Added support for Dictionary decoding. Added
=>
overloads returning[String: T]
,[String: T]?
and[Decodable: AnyObject]?
- Extension for
NSArray
- Added
[T?]?
-returning overload - Support for Swift Package Manager (#54 @neonichu)
- Explicit deployment target for tvOS and watchOS (#55 @NachoSoto)
Death of Redundancy
=>?
operator is removed, use either[T].decode(json, ignoreInvalidObjects: true)
ortry? json => "key"
=>
overload without inferred return-type will no longer be decoded asNSDictionary
. It now returnsAnyObject
instead (no decoding at all).- Fixes the semiserious #34
- A lot of target/platform/bitcode changes contributed by a lot of nice people. WatchOS, tvOS, and iOS should be supported with bitcode and Mac, as before, without it. However all of them should now work with CocoaPods.