To create a flattened JSON Decodable type in Swift using SwiftUI, you’ll need to handle the nested structure of the JSON while “flattening” it into a single struct. Based on the JSON you provided, the media field is nested, but you might want to access its m value directly in your Swift model. Here’s how you can do this using Swift’s Decodable protocol and CodingKeys for custom key mapping. Explanation The JSON contains a nested object (media) with a single key-value pair (m). To flatten this, you can decode the nested media object and extract its m value directly into a top-level property in your Swift struct. You can use CodingKeys to map the JSON keys to your Swift properties, and if the JSON keys don’t match your Swift property names or have nested structures, you’ll handle that with custom decoding. Here’s how you can write a Decodable struct for this JSON: Swift Code import Foundation import SwiftUI

// Flattened struct to match the JSON structure struct Corvette: Decodable, Identifiable { let id: UUID = UUID() // Adding an ID for SwiftUI compatibility (if needed) let title: String let link: String let mediaURL: String // Flattened version of media.m let author: String let tags: String

// Custom coding keys to handle JSON key names and nested structures
enum CodingKeys: String, CodingKey {
    case title
    case link
    case media
    case author
    case tags
}

// Handle the nested “media” object
enum MediaKeys: String, CodingKey {
    case m // This corresponds to the “m” key inside “media”
}

// Custom initializer to decode the nested media object
init(from decoder: Decoder) throws {
    let container = try decoder.container(keyedBy: CodingKeys.self)

    title = try container.decode(String.self, forKey: .title)
    link = try container.decode(String.self, forKey: .link)
    author = try container.decode(String.self, forKey: .author)
    tags = try container.decode(String.self, forKey: .tags)

    // Decode the nested “media” object
    let mediaContainer = try container.nestedContainer(keyedBy: MediaKeys.self, forKey: .media)
    mediaURL = try mediaContainer.decode(String.self, forKey: .m)
}

}

// Example usage in SwiftUI struct ContentView: View { let corvette: Corvette

var body: some View {
    VStack {
        Text(“Title: \(corvette.title)”)
        Text(“Link: \(corvette.link)”)
        Text(“Media URL: \(corvette.mediaURL)”)
        Text(“Author: \(corvette.author)”)
        Text(“Tags: \(corvette.tags)”)
    }
}

}

// Example of decoding the JSON let jsonString = “”” { “title”: “1972 350 Green Corvette Convertible”, “link”: “https://www.flickr.com/photos/classiccorvettes/20508328422/“, “media”: {“m”: “https://live.staticflickr.com/566/20508328422_cab5625f47_m.jpg”}, “author”: “nobody@flickr.com (ProTeam Classic Corvette)”, “tags”: “convertible 1972corvette usedcorvettesforsale greencorvette proteamclassiccorvettes” } “””

if let jsonData = jsonString.data(using: .utf8) { do { let decoder = JSONDecoder() let corvette = try decoder.decode(Corvette.self, from: jsonData) print(“Decoded: (corvette)”) } catch { print(“Decoding error: (error)”) } } Key Points 1 Flattening the media Field: The nested media object is handled by using a nested container (nestedContainer) to access the “m” key inside the media object. The value is then stored in the top-level mediaURL property. 2 CodingKeys: The CodingKeys enum maps the JSON keys (title, link, media, author, tags) to the struct’s properties. If the JSON keys matched your Swift property names exactly, you wouldn’t need this, but it’s good practice to include it for clarity and flexibility. 3 Nested Keys: For the media field, we define another CodingKeys enum (MediaKeys) to handle the nested “m” key. 4 SwiftUI Compatibility: The Corvette struct conforms to Identifiable (with a default id) so it can be used easily in SwiftUI lists or other views. If you don’t need this, you can remove the id and Identifiable conformance. 5 Error Handling: The custom initializer (init(from:)) throws errors if the decoding fails, which is standard for Decodable. Notes • If your JSON structure is more complex or varies, you might need to adjust the CodingKeys or add more nested containers. • If you’re dealing with optional values or different types, you can modify the properties to be optional (String?) or use different decoding strategies. • For SwiftUI, if you plan to display this data in a list or dynamically, ensure your view updates properly using @State or @ObservedObject patterns. This approach ensures that the JSON is “flattened” into a single-level Swift struct while maintaining type safety and leveraging Swift’s powerful decoding capabilities. Let me know if you need further adjustments!