使用Codable解析API数据后，如何在PickerView中获取数据及ID值

Hey there! Let's tackle your problems step by step—first the Codable parsing hurdles, then the UIPickerView loading and array access issues.

1. Resolving Codable Parsing: Can't Access Specific Values (like id) #

First, let's clean up your Codable structs to follow Swift conventions and eliminate common pitfalls that block value access:

Updated Codable Structs #

// Follow Swift naming rules: uppercase struct names, camelCase properties
struct Reasons: Codable {
    let reasonAndWhomMeet: Both?
    
    // Map snake_case JSON keys to camelCase properties (or use .convertFromSnakeCase)
    enum CodingKeys: String, CodingKey {
        case reasonAndWhomMeet = "reason_and_whom_meet"
    }
}

struct Both: Codable {
    let reasonList: [ReasonList]?
    let whomMeet: [NameList]?
    
    enum CodingKeys: String, CodingKey {
        case reasonList = "reason_list"
        case whomMeet = "whom_meet"
    }
}

// Make sure this struct includes your `id` property!
struct ReasonList: Codable {
    let id: String? // Adjust type (Int, etc.) to match your JSON
    // Add other properties from your JSON here
}

struct NameList: Codable {
    let id: String? // Same here—match your JSON's id type
    // Add other properties as needed
}

Proper Parsing & Value Access #

When decoding your API response, always unwrap optional values safely to access nested data like id:

// Assume `apiData` is the Data object from your API response
do {
    let decoder = JSONDecoder()
    // Alternative to CodingKeys: auto-convert snake_case to camelCase
    // decoder.keyDecodingStrategy = .convertFromSnakeCase
    let reasonsResponse = try decoder.decode(Reasons.self, from: apiData)
    
    // Safely unwrap nested layers to get to reasonList and its ids
    if let bothData = reasonsResponse.reasonAndWhomMeet, 
       let reasonList = bothData.reasonList {
        for reason in reasonList {
            if let reasonId = reason.id {
                print("Found reason ID: \(reasonId)")
                // Use the id here as needed
            }
        }
    }
} catch {
    print("Parsing error: \(error.localizedDescription)")
}

Common pitfalls to check:

• Did you forget to include the id property in your ReasonList/NameList structs?
• Are you failing to unwrap optional values (the ? in your structs means you need to check for nil)?
• Does your JSON structure match your Codable structs exactly? (Use a JSON viewer to verify)

2. Fixing UIPickerView Early Loading & Array Content Access #

The main issue here is likely that your PickerView is trying to load data before your API parsing is complete. Here's how to fix it:

Step 1: Define a Reactive Data Source #

Create a stored property to hold your parsed data, and update it only after parsing succeeds:

class YourViewController: UIViewController, UIPickerViewDataSource, UIPickerViewDelegate {
    // Your PickerView outlet
    @IBOutlet weak var reasonPicker: UIPickerView!
    
    // Data source for the PickerView (starts empty, gets populated post-parsing)
    private var reasonList: [ReasonList]?
    
    override func viewDidLoad() {
        super.viewDidLoad()
        reasonPicker.dataSource = self
        reasonPicker.delegate = self
        
        // Trigger your API request here
        fetchAndParseData()
    }
}

Step 2: Update Data Source & Refresh PickerView #

After successful parsing, update your data source on the main thread and reload the PickerView:

private func fetchAndParseData() {
    // Your API request code here...
    URLSession.shared.dataTask(with: yourAPIURL) { [weak self] data, _, error in
        guard let self = self, let data = data else { return }
        
        do {
            let decoder = JSONDecoder()
            decoder.keyDecodingStrategy = .convertFromSnakeCase
            let reasonsResponse = try decoder.decode(Reasons.self, from: data)
            
            // Update data source on main thread (UI updates must run here!)
            DispatchQueue.main.async {
                self.reasonList = reasonsResponse.reasonAndWhomMeet?.reasonList
                self.reasonPicker.reloadAllComponents() // Refresh PickerView with new data
            }
        } catch {
            print("Parsing error: \(error)")
        }
    }.resume()
}

Step 3: PickerView Data Source/Delegate Methods #

Use optional binding to safely access your array data in the PickerView methods:

func numberOfComponents(in pickerView: UIPickerView) -> Int {
    return 1 // Adjust based on your needs
}

func pickerView(_ pickerView: UIPickerView, numberOfRowsInComponent component: Int) -> Int {
    return reasonList?.count ?? 0 // Return 0 if data isn't loaded yet
}

func pickerView(_ pickerView: UIPickerView, titleForRow row: Int, forComponent component: Int) -> String? {
    guard let reason = reasonList?[row], let id = reason.id else {
        return nil // Return nil if data isn't ready
    }
    return id // Or return another field (like a name) if needed
}

// Access selected row's id
func pickerView(_ pickerView: UIPickerView, didSelectRow row: Int, inComponent component: Int) {
    guard let reason = reasonList?[row], let selectedId = reason.id else {
        return
    }
    print("Selected reason ID: \(selectedId)")
    // Use the selected id here (e.g., update a label, save to a variable)
}

Key fixes here:

• Your PickerView no longer loads empty data upfront—wait until parsing is done to populate the data source.
• Using reloadAllComponents() ensures the PickerView refreshes once new data is available.
• Safe optional binding prevents crashes if data isn't ready yet.

内容的提问来源于stack exchange，提问作者NiranjanB