Extending ParseUser

[aruvalcaba]

Is this possible? I have tried for ParseObjects and that worked fine, for ParseUser no.

[gfosco]

What did you try and what did not work?

[aruvalcaba]

Ive tried just as the subclassing documentation has mentioned

class User extends ParseUser{
    public static $parseClassName = "_User";
}

Called User::registerSubclass() before calling any other functions.

I called a function such as User::getCurrentUser() and I get an error, but I guess this is due to the scope of the particular variable $currentUser

[gfosco]

Ok, it looks like you can't currently subclass from ParseUser.. They are stored by the class name, and _User is assigned to ParseUser. Can you tell me a little about your use case for subclassing ParseUser?

[aruvalcaba]

It's not necessary, I just wanted to add some more functions to work with a ParseUser.

[gfosco]

Ok.. I'll leave this open as a feature request.

[francimedia]

I think there is a general error in the way how the php class names and parse class names are approached. The mapping fails for _User, _Role and _Installation.

I added some hacks to get it working, but it's not a good implementation.
Please check theses tests: https://github.com/francimedia/parse-php-sdk

Example implementation:

<?php namespace MyParseModels; use Parse\ParseQuery; use Parse\ParseUser as BaseParseUser; use Parse\ParseClient; class ParseUser extends BaseParseUser { public static $parseClassName = "_User"; protected static $currentUser = null; public function helloWorld() { return 'Hello World!'; } }

<?php use MyParseModels\ParseUser; use Parse\ParseClient; ParseUser::registerSubclass(); ParseClient::initialize(...); print_r(ParseUser::getCurrentUser());

[hipsterjazzbo]

I'd really like this as well for a number of reasons:

1. I like to subclass so that I can docblock the subclasses and get property autocompletion/documentation
2. I'm using the repository pattern, and can't really do it very well without subclassing the built in ParseUser class
3. I like to add relationship methods to my subclasses, to ease retrieving children from the parent (get all the Comments for a Post for example). Can't do that for users without subclassing.

Just my $0.02

[hipsterjazzbo]

@gfosco Found another fantastic reason to make this work: I'm building a package to integrate Parse pretty tightly with Laravel, and in order to do the authentication properly, I'll need this to extend the ParseUser object with a few more methods.

[hipsterjazzbo]

So I've just gone ahead and done this. I'll open a PR once you've merged #80, so that I don't have to rebase with the new PSR-2 code style.

[gfosco]

Closing this, it will be covered in #84.