feat: Add $setOnInsert operator to Parse.Server.database.update

[mtrezza]

Pull Request

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

Issue

Closes: #8792

Approach

Add support for $setOnInsert.

Tasks

• Add 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

Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (686a9f2) 94.11% compared to head (9f44f35) 94.09%.
Report is 1 commits behind head on release-5.x.x.

❗ Current head 9f44f35 differs from pull request most recent head 8eb1866. Consider uploading reports for the commit 8eb1866 to get more accurate results

Additional details and impacted files

@@                Coverage Diff                @@
##           release-5.x.x    #8790      +/-   ##
=================================================
- Coverage          94.11%   94.09%   -0.03%     
=================================================
  Files                184      184              
  Lines              13809    13814       +5     
=================================================
+ Hits               12997    12998       +1     
- Misses               812      816       +4     

Files	Coverage Δ
src/Adapters/Storage/Mongo/MongoTransform.js	88.31% <66.66%> (-0.11%)	⬇️
src/Controllers/DatabaseController.js	93.70% <0.00%> (-0.27%)	⬇️

... and 1 file with indirect coverage changes

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

[parseplatformorg]

🎉 This change has been released in version 5.6.0

[oallouch]

Hi,
I can't find the corresponding API change in the JS SDK.

[mtrezza]

This is a Cloud Code only feature.

[oallouch]

So the API has to be so low level ? I could be wrong, but the js sdk is also for Cloud Code.
Are we supposed to write "__op" in our code ?

[mtrezza]

Parse.Server gives you access to undocumented APIs, with various levels, ranging from just below the official Parse APIs down to the raw MongoDB driver. In the case of this issue here, there is no Parse SDK involved (apart from the namespace); this is operating on the internal database adapter level. If you decide to use this, extensive testing is advised, see also #8786.

[oallouch]

Very interesting.
I still use Config.get(Parse.applicationId).database