Tree Parse object

[boardmain]

Hi i have a Tree object

with parent is object of the same type

how can i solve this?

struct Pagina : ParseObject {
    var objectId: String?
    var createdAt: Date?
    var updatedAt: Date?
    var ACL: ParseACL?
    var titolo: [String: String]?
    var parent: Pagina? <--- i can't do this because we are in a struct...
}

[cbaker6]

You cannot do this with a struct as the compiler will not allow it, plus you can easily create a cycle.

A class can do this, but this SDK isn’t designed for classes, so you will most likely run into threading issues. Still shouldn’t do this because of the cycle I mentioned earlier.

A workaround would be change the parent property to parentObjectId: String? and store the objectId of the parent. Whenever you need the parent, fetch it based off the objectId

[boardmain]

You cannot do this with a struct as the compiler will not allow it, plus you can easily create a cycle.

A class can do this, but this SDK isn’t designed for classes, so you will most likely run into threading issues. Still shouldn’t do this because of the cycle I mentioned earlier.

A workaround would be change the parent property to parentObjectId: String? and store the objectId of the parent. Whenever you need the parent, fetch it based off the objectId

yes i think for now can i only do that :/

thank you

[cbaker6]

You also might be able to get away with:

struct Pagina : ParseObject {
    var objectId: String?
    var createdAt: Date?
    var updatedAt: Date?
    var ACL: ParseACL?
    var titolo: [String: String]?
    var parent: Pointer<Pagina>? //This will always have to be a pointer instead of an object. The same way it's represented on the server.
}

This should work for when you already created your schema using a different parse SDK that uses classes (almost all of them except for the Swift SDK) that uses parent as a property. You will still need to fetch parent manually in order to access all of the properties of the parent.

In the future, I don't recommend saving the same "Parse Class" type to a "Parse Class" for the reasons I mentioned before.

Update: If you use this way, be sure you are using Swift SDK 1.8.3+