For the complete documentation index, see llms.txt. This page is also available as Markdown.

Subclasses

Subclassing is completely optional, however it has many advantages, including terseness, extensibility, and support for autocomplete. In Symbyoz you can automatically generate subclasses of your Modules, in Swift and Java , from the Configuration section of your backend.

It will literally transforms this code:

ParseObject object = new ParseObject("ClassName");
object.put("displayName", "John Doe");
object.put("isFunny", false);
object.put("age", 50);
var object = PFObject(className:"ClassName")
object["displayName"] = "John Doe"
object["isFunny"] = false
object["age"] = 50

Into this:

ClassName object = new ClassName();
object.setDisplayName("John Doe");
object.setIsFunny(false);
object.setAge(50);
var object = ClassName()
object.displayName = "John Doe"
object.isFunny = false
object.age = 50

Creating Subclass

Follow this example to have your own subclass ready to use.

  1. Create your class as following

ClassName.java
import com.parse.ParseClassName;
import com.parse.ParseObject;

@ParseClassName("ClassName")
public class ClassName extends ParseObject
{
  public String getDisplayName() 
  {
    return getString("displayName");
  }
  
  public void setDisplayName(String value) 
  {
    put("displayName", value);
  }
}
import Foundation
import Parse

class Address: PFObject, PFSubclassing
{
    @NSManaged var media:  PFFile?
    @NSManaged var fullAddress:  String?
    @NSManaged var street:  String?
    @NSManaged var googlePlaceId:  String?
    @NSManaged var city:  String?
    @NSManaged var streetNumber:  String?
    @NSManaged var isDeleted:  Bool
    @NSManaged var owner:  PFUser?
    @NSManaged var location:  PFGeoPoint?
    @NSManaged var country:  String?
    @NSManaged var postalCode:  String?
    @NSManaged var comment:  String?
    @NSManaged var isBillingAddress:  Bool
        
    override init()
    {
        Address.registerSubclass()
        super.init()
    }
    
    static func parseClassName() -> String
    {
        return "Address"
    }
}

2. Register your class before you initialize Parse in your Application class

And you're all done!

Now you can simply use it as you would use any other Object but with a structured model and accessor added.

Last updated

Was this helpful?