feat: Add transaction to save and destroy on Parse.Object

[vahidalizad]

Pull Request

• Report security issues confidentially.
• Any contribution is under this license.
• Link this pull request to an issue.

Issue

This pull request addresses issues related to performing batch transactions.
Closes: #922

Approach

• Added a transaction option to the save and destroy methods in the ParseObject class.
• Implemented checks to ensure objects are serializable before creating a batch, as the server cannot save children and parents simultaneously in a single transactional batch.

Tasks

• Add a transaction option to save and destroy in the ParseObject class.
• Ensure that objects are serializable before initiating a batch save, as transactional operations require the batch size to match the entire input.
• Add relevant tests.

[parse-github-assistant]

I will reformat the title to use the proper commit message syntax.

[parse-github-assistant]

Thanks for opening this pull request!

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (b50790a) to head (4c1534e).
Report is 168 commits behind head on alpha.

Additional details and impacted files

@@            Coverage Diff             @@
##             alpha     #2265    +/-   ##
==========================================
  Coverage   100.00%   100.00%            
==========================================
  Files           61        64     +3     
  Lines         6186      6392   +206     
  Branches      1499      1520    +21     
==========================================
+ Hits          6186      6392   +206     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[vahidalizad]

@mtrezza Could you please check and review the changes when you have a chance?

[mtrezza]

Looks good; let's see if someone from the JS team has any feedback before we merge. Btw, would you be interested to get team to get notified when someone is requesting feedback on their PR?

Is this a fix or a feature? From the issue description it looks more like a new feature?

[vahidalizad]

Looks good; let's see if someone from the JS team has any feedback before we merge. Btw, would you be interested to get team to get notified when someone is requesting feedback on their PR?

Is this a fix or a feature? From the issue description it looks more like a new feature?

Thanks for the feedback! I agree, this is more of a feature than a fix.
Regarding the notification for the team when someone is requesting feedback on their PR, could you clarify how that would work? I'm not sure I fully understand the suggestion.

[mtrezza]

Regarding the notification for the team when someone is requesting feedback on their PR, could you clarify how that would work? I'm not sure I fully understand the suggestion.

You'd just be added to the review team here on GitHub. When someone submits a PR and the PR is ready for review, then you'd get a notification and if you have some time you can look over it and provide feedback. No obligation though.

[vahidalizad]

You'd just be added to the review team here on GitHub. When someone submits a PR and the PR is ready for review, then you'd get a notification and if you have some time you can look over it and provide feedback. No obligation though.

Sure, thanks for the trust! I'd be happy to help as much as I can.

[parseplatformorg]

🎉 This change has been released in version 5.3.0-alpha.4