Selector naming isn't a replacement for documentation, unless you happen to know how to express invariants like these entirely through naming and the type system:
"Property keys must be <code>NSString</code> objects and values must be serializable."
Also, I think the problem you might be having is that you're trying to hold other people's software to the constraints of your particular way of using a 13" consumer laptop.
You're angry about this? https://github.com/amplitude/Amplitude-iOS/blob/master/Ampli...
Selector naming isn't a replacement for documentation, unless you happen to know how to express invariants like these entirely through naming and the type system:
"Property keys must be <code>NSString</code> objects and values must be serializable."
Also, I think the problem you might be having is that you're trying to hold other people's software to the constraints of your particular way of using a 13" consumer laptop.