调用setValueForKey前如何验证类型？兼容Int转Double场景

Great question! The problem with your strict type equality check is that it’s too rigid—it blocks the implicit type conversions that KVC’s setValueForKey: natively handles (like Int → Double). Instead of reinventing the wheel with manual type checks, you can leverage KVC’s built-in validation system to safely determine if a value can be converted to your property’s type.

The Best Approach: Use validateValue(_:forKey:) #

Every NSObject subclass (which you’re using since you’re calling setValueForKey:) has access to the validateValue(_:forKey:) method. This method does exactly what you need:

• It checks if the value can be converted to the property’s type (following KVC’s own conversion rules).
• If conversion is possible, it returns true and updates the passed-in value to the converted type.
• If conversion fails, it returns false and provides an error explaining why.

Example Implementation #

Let’s walk through a concrete example. First, define your model class:

class MyModel: NSObject {
    @objc var temperature: Double = 0.0
    @objc var name: String = ""
    @objc var count: Int = 0
}

Now, safely set properties from a dictionary using validation:

let model = MyModel()
let dataDict: [String: Any] = [
    "temperature": 25, // Int → Double (valid)
    "name": 12345, // NSNumber → String (valid)
    "count": "not-a-number", // String → Int (invalid)
    "temperature": "22.5" // String → Double (valid)
]

for (key, rawValue) in dataDict {
    var mutableValue: Any? = rawValue
    var validationError: NSError?
    
    if model.validateValue(&mutableValue, forKey: key) {
        model.setValue(mutableValue, forKey: key)
        print("Successfully set \(key): \(mutableValue!)")
    } else {
        let errorMsg = validationError?.localizedDescription ?? "Unknown validation error"
        print("Failed to set \(key) with value \(rawValue): \(errorMsg)")
    }
}

What This Handles Automatically #

This method covers all the type conversions KVC supports, including:

• Numeric type conversions (Int ↔ Double ↔ Float)
• String ↔ NSNumber conversions (for valid numeric strings)
• NSNumber ↔ String conversions
• Boolean conversions (e.g., Int(1) → Bool(true), "false" → Bool(false))

Why This Is Better Than Manual Checks #

Writing manual type checks is error-prone—you’d have to account for every possible conversion KVC supports, which is a lot. Using validateValue(_:forKey:) ensures you’re using the exact same logic as setValueForKey: itself, so you never accidentally block a valid conversion or allow an invalid one that would cause a crash.

Handling Validation Failures #

When validation fails, you can choose how to handle it based on your app’s needs:

• Set a default value for the property
• Log the error for debugging
• Skip the property entirely
• Show a user-facing error message (if the data comes from user input)

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