Properly store User Subclass in Storage (#978)

* Failing test for subclass.current()

* ensure subclass user class is saved to storage

* fix failing test

Author: dplewis

integration/test/ParseUserTest.js

@@ -630,6 +630,22 @@ describe('Parse User', () => {
     expect(user.get('foo')).toBe('bar');
   });
 
+  it('can get current with subclass', async () => {
+    Parse.User.enableUnsafeCurrentUser();
+
+    const customUser = new CustomUser({ foo: 'bar' });
+    customUser.setUsername('username');
+    customUser.setPassword('password');
+
+    await customUser.signUp();
+    Parse.User._clearCache();
+
+    const user = CustomUser.current();
+    expect(user instanceof CustomUser).toBe(true);
+    expect(user.doSomething()).toBe(5);
+    expect(user.get('foo')).toBe('bar');
+  });
+
   it('can logIn user with subclass', async () => {
     Parse.User.enableUnsafeCurrentUser();
 

src/ParseUser.js

@@ -869,7 +869,7 @@ const DefaultController = {
   updateUserOnDisk(user) {
     const path = Storage.generatePath(CURRENT_USER_KEY);
     const json = user.toJSON();
-    json.className = '_User';
+    json.className = user.constructor.name === 'ParseUser' ? '_User' : user.constructor.name;
     return Storage.setItemAsync(
       path, JSON.stringify(json)
     ).then(() => {