Skip to content
This repository was archived by the owner on Jun 13, 2023. It is now read-only.

parseObject method can't parse complex PFObjects #64

Closed
agordeev opened this issue Sep 8, 2016 · 1 comment
Closed

parseObject method can't parse complex PFObjects #64

agordeev opened this issue Sep 8, 2016 · 1 comment

Comments

@agordeev
Copy link
Contributor

agordeev commented Sep 8, 2016

Hi @richardjrossiii , is it possible to improve parseObject<T: PFObject>(objectDictionary: [String:AnyObject]) method, so it correctly parses complex PFObjects? Currently it even leaves PFACL as a plain dictionary, which causes an error on saving the object later ([NSCFDictionary hasUnresolvedUser] unrecognized selector sent to instance)

I was thinking of using (instancetype)ACLWithDictionary:(NSDictionary *)dictionary method, but it seems marked as a private.

Is there a way to use a standard Parse iOS SDK for parsing the server's response to PFObject?

@richardjrossiii
Copy link
Contributor

The initial plan was to make PFEncoder/PFDecoder from the core SDK public classes, and if you were to publicize the headers for that (or port that logic to swift), you probably could make that work.

Other than that, there's no methods on PFObject that I'm aware of (private or otherwise) that allow you to construct it from it's REST representation.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants