feat: Add Cloud Function execution on Parse Object in data browser

[dblythy]

New Pull Request Checklist

• I am not disclosing a vulnerability.
• I am creating this PR in reference to an issue.

Issue Description

Adds a scripts context menu that can call custom cloud code scripts with req.params.object. A small server update will be needed to allow Pointers to be passed.

Closes: #2399

Approach

TODOs before merging

[parse-github-assistant]

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

[parse-github-assistant]

Thanks for opening this pull request!

• 🎉 We are excited about your hands-on contribution!

[dblythy]

mov.mov

[dblythy]

The Parse Cloud code for this would be:

Parse.Cloud.define('deleteAccount', async (req) => {
  req.params.object.set('deleted', true);
  await req.params.object.save(null, {useMasterKey: true});
}, {
  requireMaster: true
});

With the scripts config:

"scripts": [
  {
    "title": "Delete account",
    "classes": ["_User"],
    "cloudCodeFunction": "deleteAccount"
  }
]

[uffizzi-cloud]

Uffizzi Ephemeral Environment deployment-20722

⌚ Updated Mar 30, 2023, 05:07 UTC

☁️ https://app.uffizzi.com/github.com/parse-community/parse-dashboard/pull/2409

📄 View Application Logs etc.

What is Uffizzi? Learn more

[mtrezza]

This is just an amazing feature, great work!

[mtrezza]

This feature requires a certain version of Parse Server to work properly (parse-community/parse-server#8490). The compatibility table in the README needs to be updated to indicate which version of Parse Server is required for this feature.

[dblythy]

I have updated the README

[mtrezza]

I'm unsure how we should define the compatibility when only 1 feature requires a certain Parse Server version.

• If we apply it to the whole release then we are forcing people to upgrade their server even though they may not use the feature.
• If we apply it to the feature only in the README, then a dashboard user may be in doubt which features they can actually use.

I think the best would be if use the Parse Server version (which the dashboard knows) and based on that we hide the feature, or only disable it with a tool tip "Requires Parse Server >=...". Not sure how difficult that is?

[uffizzi-cloud]

Uffizzi Ephemeral Environment deployment-27982

⌚ Updated Jun 08, 2023, 19:29 UTC

☁️ https://app.uffizzi.com/github.com/parse-community/parse-dashboard/pull/2409

📄 View Application Logs etc.

What is Uffizzi? Learn more

[dplewis]

@dblythy Damn Daniel (always wanted to say that) let me check this branch out.

[mtrezza]

@dblythy we've always been mentioning pointers which cause the issue in Parse Server. I though of it like pointers within a Parse Object, that point to another object. But from the examples in the README it seems that the object itself needs to be transformed from POJO to a Parse.Object instance. Could you clarify this, so we know what changes are necessary in the README for this to get merged.

Also I'd like to clarify this to write up a proper changelog entry and API doc for the temp option for the fix in Parse Server parse-community/parse-server#8646.

[dblythy]

But from the examples in the README it seems that the object itself needs to be transformed from POJO to a Parse.Object instance

Yes, that is correct. Cloud code currently has no way to decode a pointer that is sent in a payload, it is always interpreted as a POJO. There is not a current mechanism to do the following:

Parse.Cloud.define("updateObject", async req => {
  req.params.object.increment("count"); // req.params.object with be a POJO so Parse Object prototypes will throw
  await req.params.object.save(null, { useMasterKey: true });
});
const object = await new Parse.Object("Test").save();
await Parse.Cloud.run("updateObject", { object }); // throws Parse Objects not allowed here, so let's use object.toPointer() instead

Therefore, currently it's up to the developer to transform the payload, such as:

Parse.Cloud.define("updateObject", async req => {
  const object = Parse.Object.extend("Test").createWithoutData(req.params.id);
  object.increment("count");
  await object.save(null, { useMasterKey: true });
});
const obj = await new Parse.Object("Test").save();
await Parse.Cloud.run("updateObject", { id: obj.id });

So, as there's no way to implicitly pass Parse Objects to cloud code (hence why we needed a server PR)

[mtrezza]

Got it, changes in parse-community/parse-server#8646 made accordingly. So we can go ahead and merge this.

[mtrezza]

Ready for merge, waiting for CI to pass...

[parseplatformorg]

🎉 This change has been released in version 5.2.0-alpha.19

[parseplatformorg]

🎉 This change has been released in version 5.3.0-beta.1

[parseplatformorg]

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

[parseplatformorg]

🎉 This change has been released in version 5.3.0