Parsing in Swift: a DTO-based Approach

Turning JSON into actual Swift types is something most apps have to deal with eventually. At the beginning of Swift, Apple was not opinionated about how we should approach that task. So people came up with a bunch of <a href="https://github.com/JohnSundell/Unbox" rel="noopener ugc nofollow" target="_blank">different</a> <a href="https://github.com/tristanhimmelman/ObjectMapper" rel="noopener ugc nofollow" target="_blank">libraries</a> to do so. Some of them are <a href="https://github.com/thoughtbot/Argo" rel="noopener ugc nofollow" target="_blank">quite esoteric</a>. Fortunately, Apple came up with its own first-party solution, <a href="https://developer.apple.com/documentation/swift/codable#" rel="noopener ugc nofollow" target="_blank">Codable</a>. Turning JSON into Swift types can be as easy as conforming those types to the <code>Codable</code> protocol. You might not need to do anything else. The compiler will do its magic and synthesize the appropriate parsing code for you. That’s lovely. There’s no better code than the one you don’t have to write. Sometimes, the “parsing code” you have to write is minimal, providing a <code>CodingKeys</code> enum with the appropriate mapping between your type property names and the JSON keys. <a href="https://betterprogramming.pub/parsing-in-swift-a-dto-based-approach-5edca55eb57a">Website</a>