codable

I have a struct that parse JSON using Codable . struct Student: Codable { let name: String? let amount: Double? let adress: String? } Now if the amount value is coming as null the JSON parsing is failing. So should I manually handle the null cases for all the Int and Double that are present in the Student struct? The String values coming as null is automatically handled. Let me do this Playground for you since an example shows you more than a hundred words: import Cocoa struct Student: Codable { let name: String? let amount: Double? let adress: String? } let okData = """ { "name": "here",

I've created a "codable" struct to serialize a data set and encode it to Json. Everything is working great except the computed properties don't show in the json string. How can I include computed properties during the encode phase. Ex: struct SolidObject:Codable{ var height:Double = 0 var width:Double = 0 var length:Double = 0 var volume:Double { get{ return height * width * length } } } var solidObject = SolidObject() solidObject.height = 10.2 solidObject.width = 7.3 solidObject.length = 5.0 let jsonEncoder = JSONEncoder() do { let jsonData = try jsonEncoder.encode(solidObject) let jsonString

Let's say that I have a model like the following, which allows me to build a tree of Foo objects. struct Foo { var kind : Kind enum Kind { case node([Foo]) case leaf } } How can I make this Codable, specifically for the case node([Foo]) ? Here's the final struct, based on the answer from @PauloMattos: Base Foo struct: struct Foo { var name: String var kind: Kind enum Kind { case node([Foo]) case leaf } init(name: String, kind: Kind) { self.name = name self.kind = kind } } Codable Protocol extension: extension Foo : Codable { enum CodingKeys: String, CodingKey { case name case nodes } enum

I am attempting to render a view from data returned from an API endpoint. My JSON looks (roughly) like this: { "sections": [ { "title": "Featured", "section_layout_type": "featured_panels", "section_items": [ { "item_type": "foo", "id": 3, "title": "Bisbee1", "audio_url": "http://example.com/foo1.mp3", "feature_image_url" : "http://example.com/feature1.jpg" }, { "item_type": "bar", "id": 4, "title": "Mortar8", "video_url": "http://example.com/video.mp4", "director" : "John Smith", "feature_image_url" : "http://example.com/feature2.jpg" } ] } ] } I have an object that represents how to layout a

Why am I getting a "Type 'Bookmark' does not conform to protocol 'Decodable'" error message? class Bookmark: Codable { weak var publication: Publication? var indexPath: [Int] var locationInText = 0 enum CodingKeys: String, CodingKey { case indexPath case locationInText } init(publication: Publication?, indexPath: [Int]) { self.publication = publication self.indexPath = indexPath } } I do not wish to save the publication var since the Publication owns the Bookmark but the bookmark needs to know which Publication it belongs to. The decode init of Publication will set the bookmark reference to

I'd like to decode an XML document using the new Decodable protocol introduced in Swift 4, however, there doesn't seem to be an existing implementation for an XML decoder that conforms to the Decoder protocol. My plan was to use the SWXMLHash library to parse the XML, then possibly make the XMLIndexer class in that library extend the Decoder protocol so that my model can be initialized with an instance of XMLIndexer ( XMLIndexer is returned by SWXMLHash.parse(xmlString) ). My issue is that I have no clue how to implement the Decoder protocol and I can't seem to find any resources online that

Swfit 4's new Encodable / Decodable protocols make JSON (de)serialization quite pleasant. However, I have not yet found a way to have fine-grained control over which properties should be encoded and which should get decoded. I have noticed that excluding the property from the accompanying CodingKeys enum excludes the property from the process altogether, but is there a way to have more fine-grained control? The list of keys to encode/decode is controlled by a type called CodingKeys (note the s at the end). The compiler can synthesize this for you but can always override that. Let's say you