Decodable

Decodable copied to clipboard

Ambigous operator => xcode 13

2

Hi, I tried running decodable on xcode 13 and getting error wherever kepath operators being used => showing error Ambigous operator. How to solve this.

dash-1234

Use preferred capitalization of CocoaPods. Change ErrorProtocol to Error. Fix typos.

ryandesign

While profiling app , it fails .

1

Fails with No Such module as Decodable. But when I run it installs fine and can distribute the app to appstore too. import protocol Decodable.Decodable

Ankish

Future of Decodable

5

- Would it be possible to gracefully migrate our syntax to rely on Swift 4's `Codable` instead? - Would there even be a point in doing that? (yes?)

Anviking

'Decodable' naming conflict in Swift 4

9

Swift 4 includes a built in `Decodable` protocol. Tried to build my project in Swift 4/Xcode 9 and got naming conflicts all over the place. Obviously, it's early, but wanted...

chrismanderson

This is an experiment to see what happens when we remove all existing functionality and rely on Swift 4's `Codable` instead. - [x] Remove all existing functionality - [x] Create...

Anviking

Redundant conformance of 'CGPoint' to protocol 'Decodable'

1

I'm getting this error when trying to build the project for `Test` target: The code is: ```swift extension CGPoint: Decodable { /// Decodes CGPoint from JSON array. Returns CGPoint.zero if...

agordeev

KeyPath Class name ambiguous in xcode 9

1

Ankish

Initialise one object from different JSON sources.

12

Say we have an object, which should be initialised from a JSON coming over the network and from a different JSON e.g. coming from the disk. This is currently not...

lutzmi

Unable to "ignore" an element. Instead it always throws

1

I have an array of dictionaries, each with a "Type" field that is used to determine which struct should be used for decoding it. Currently I have some unsupported types....

mdonati