When creating or saving the parse object add feature to include sub parse object fetch operation.

[zahidshaikh08]

New Feature / Enhancement Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.

Current Limitation

Currently when we save or create any new parse objects from sdk after successful response from server we again have to get the same object from server via QueryBuilder's new query.

This is creating following issues :

1. An extra api call for every saved object on server to retain the sub parse objects in any particular parse object.
2. Newly or existing parse objects lost its new/existing values after saving on server.

Feature / Enhancement Description

To resolve this issue i think we should have a include like feature/option in save(), so that every time we save the parse object its corresponding response that is response.result or response.results includes sub parse objects values to avoid an extra api call to get the same information from server after successful response.

Example Use Case

Example 1 :

My user model has list meta data models, so every time I add new meta data model to user's parse object with the required info after saving it i have to again fetch the new current user model from server to fill the values of List into UserModel to have all the subParseObjects.

[parse-github-assistant]

Thanks for opening this issue!

• 🎉 We are excited about your ideas for improvement!

[zahidshaikh08]

Any updates on this issue?