Swift - SRKObject field values not settable in any init methods

[MeteC]

Porting an Obj-C SRKObject implementation over to Swift today, I found my tests started failing. It turned out I couldn't use any custom init methods (nor convenience init) to provide any values for my @objc dynamic vars. Those values are simply overwritten with 0. (Something that wasn't happening in Objective-C.)

e.g. something like @objc public convenience init(withID: NSNumber, dataType: Int) fails to initialise either ID or dataType at all - within the init function the instance variables are set correctly, but upon leaving the init function they seem to be reset to 0.

Through this issue I discovered that I need to use override class func defaultValuesForEntity() -> [String : Any]? {} to provide default values on init.. So that's useful. But now I really need to put up post-it notes (literally or figuratively) to remind myself in future that I can't use custom init methods with SRKObjects in Swift.

So there's no loss of functionality ultimately, but this could definitely be a potential source of strange bugs if one's unit test coverage isn't pedantic ;-)

[editfmah]

Sadly this is a long known about bug which apple have categorically told me they don’t care about. But yeah, maybe a rethink on a good init overload, or a closure to execute to set default values maybe.

Open to suggestions?

https://stackoverflow.com/questions/37623385/timing-issues-with-swift-class-with-dynamic-variable-which-inherits-from-object

[MeteC]

Interesting! And what a pain in the butt.

Possibly a simple SRKObject baseclass init method like initWithInitialValues:(nullable NSDictionary<NSString*,id>*) values, used like defaultValuesForEntity, that internally performs a regular init and then populates values? People could then call that via super wrapped in their own init methods using safer typed arguments. I'm just riffing here I'm not sure if that's going to run into the same issue since it all comes back to init... 🤔