Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
3 tasks done
zahidshaikh08 opened this issue Jul 1, 2023 · 2 comments
Labels
type:bug Impaired feature or lacking behavior that is likely assumed

Comments

@zahidshaikh08
Copy link

New Feature / Enhancement Checklist

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
Copy link

Thanks for opening this issue!

  • 🎉 We are excited about your ideas for improvement!

@mbfakourii mbfakourii added the type:bug Impaired feature or lacking behavior that is likely assumed label Dec 20, 2023
@zahidshaikh08
Copy link
Author

Any updates on this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Impaired feature or lacking behavior that is likely assumed
Projects
None yet
Development

No branches or pull requests

2 participants