The Parse documentation for adding properties and methods on PFObject subclasses conveniently skips the Swift syntax in their sample code listing just the Objective-C syntax:
https://parse.com/docs/ios_guide#subclasses-properties/iOS
// Armor.h
@interface Armor : PFObject<PFSubclassing>
+ (NSString *)parseClassName;
@property (retain) NSString *displayName;
@end
// Armor.m
@dynamic displayName;
Has anyone figured out a work around for Swift's lack of dynamic synthesizers in order to implement properties and methods with PFSubclassing? I want to be able to do something like:
class Armor : PFObject, PFSubclassing {
class func parseClassName() -> String! {
return "Armor"
}
}
var armor = Armor()
armor.displayName = "Iron Clad"
I ran into the same issue, though I should note that your class definition should look more like this:
I tried a few different things without success. It doesn't look like the Parse SDK supports this yet, keep in mind that the current release of the Parse iOS SDK predates the swift announcement. Sounds like they're working on better swift support for an upcoming release though.
Instead, you can still create PFObject subclasses (as you did) and access data with
.getObjectForKey("displayName")
, or write your own class methods to access this data. The biggest missing piece is really just some convenience methods that the SDK usually creates for you.I had this same problem. Had to add @NSManaged to the properties I wanted saved:
Hopefully this is resolved in the next update.
Prototypic is correct. As of right now it won't work with the dynamic attribute, but the code sample doesn't include the registerSubclass Parse recommends, so the code should include it like this:
(Note that "override" is required but missing from the Parse documentation.)
Swift 1.2
First: Create a swift file and define the subclass. Don't forget to import Parse! (for example Armor)
Note: You can define your properties as optionals. Every "undefined" value inside the Parse Core Manager will be translated to "nil".
Second: Register all subclasses, inside your AppDelegate.swift.
The solution is to use computed properties instead of stored properties: