Optimize ParseObject

[yulingtianxia]

We should refer to other official API, such as iOS/OSX sdk:
https://parseplatform.org/Parse-SDK-iOS-OSX/api/Classes/PFObject.html

Creating a ParseObject

• ParseObject()

Managing Object Properties

• parseClassName //(Need refactor)
• objectId
• updatedAt
• createdAt
• ACL

Accessors

remove conflicts with existing methods.

• get
• set
• remove
• getRelation
• revertAll
• revert

Array Accessors

remove conflicts with existing methods.

• add
• addAll
• addUnique
• addAllUnique
• remove
• removeAll

Increment

• increment //(Need refactor)
• decrement //(Need refactor or delete)

Saving Objects

• save //(Need refactor)
• saveEventually

Saving Many Objects(Static Method)

• saveAll

Deleting Many Objects(Static Method)

• deleteAll

Getting Many Objects(Static Method)

• fetchAll //(Has replacement getAll，Need refactor)
• fetchAllIfNeeded

Getting an Object

• dataAvailable
• fetch //(Has replacement getObject，Need refactor)
• fetchIfNeeded

Fetching From Local Datastore

• fetchFromLocalDatastore

Deleting an Object

• delete
• deleteEventually

Dirtiness

• dirty({String key})

Pinning

• pin({String name, dynamic callback}) //(Need refactor)

Pinning Many Objects(Static Method)

• pinAll({String name, dynamic callback})

Unpinning

• unpin({String name, dynamic callback}) //(Need refactor)

Unpinning Many Objects(Static Method)

• unpinAll({bool recursively, String name, dynamic callback})

Methods for Subclasses(Static Method)

• object
• objectWithoutDataWithObjectId
• registerSubclass
• query()

[fischerscode]

registerSubclass would be great.

Maybe changing fomJson in ParseBase could do the trick.
Any ideas?

[fischerscode]

Maybe getting close to the official repos is not that good.
There are some cases where having the android like subclass system is not the best.

[fischerscode]

The registerSubclass feature got merged with #368

[parse-github-assistant]

The label type:feature cannot be used in combination with type:improvement.