feat: Add support for script execution invoking dashboard form for user input#3201
Merged
mtrezza merged 9 commits intoparse-community:alphafrom Feb 10, 2026
Merged
Conversation
|
🚀 Thanks for opening this pull request! |
Contributor
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
📝 WalkthroughWalkthroughAdds form-response handling to script execution: cloud functions can return a ScriptResponse form for user input, shown once for the first probed object; collected form data is then applied to execute the script callback across all selected objects. Documentation for Scripts was reorganized and expanded. Changes
Sequence DiagramsequenceDiagram
participant User
participant Browser as Browser Component
participant ScriptUtils as Script Utilities
participant CloudFn as Cloud Function
participant Modal as ScriptResponseModal
User->>Browser: Execute script on multiple rows
Browser->>ScriptUtils: executeScript (probe first object, pass onFormResponse)
ScriptUtils->>CloudFn: Invoke Cloud Function (objectId, payload)
CloudFn-->>ScriptUtils: Return ScriptResponse (contains form)
ScriptUtils->>Browser: onFormResponse({response, script, className, objectIds})
Browser->>Modal: Render ScriptResponseModal with form
User->>Modal: Fill form and submit
Modal->>Browser: onConfirm(formData)
Browser->>ScriptUtils: executeScriptCallback(cloudFn, className, objectIds, payload, formData)
loop per object
ScriptUtils->>CloudFn: Invoke callback for object with formData
CloudFn-->>ScriptUtils: Return result / error
ScriptUtils->>Browser: Emit per-object showNote (success/error)
end
ScriptUtils->>Browser: Trigger onRefresh/onRefreshObjects as needed
Browser->>User: Update UI / notes
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
No actionable comments were generated in the recent review. 🎉 Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
src/dashboard/Data/Browser/Browser.react.js (1)
2059-2076:⚠️ Potential issue | 🟡 Minor
scriptResponseModalis not included inhasExtras().The
hasExtras()result is passed asdisableKeyControlstoDataBrowser. SincescriptResponseModalisn't checked here, keyboard shortcuts may fire while theScriptResponseModalis open. Note thatshowExecuteScriptRowsDialogis also absent, so this may be a pre-existing gap—but worth addressing for the new modal.♻️ Proposed fix
return !!( this.state.showCreateClassDialog || this.state.showAddColumnDialog || this.state.showRemoveColumnDialog || this.state.showDropClassDialog || this.state.showExportDialog || this.state.showExportSchema || this.state.rowsToDelete || this.state.showAttachRowsDialog || this.state.showAttachSelectedRowsDialog || this.state.showCloneSelectedRowsDialog || this.state.showEditRowDialog || this.state.showPermissionsDialog || - this.state.showExportSelectedRowsDialog || - this.state.showAddToConfigDialog + this.state.showExportSelectedRowsDialog || + this.state.showAddToConfigDialog || + this.state.scriptResponseModal || + this.state.showExecuteScriptRowsDialog );
🤖 Fix all issues with AI agents
In `@README.md`:
- Around line 1382-1556: Replace the incorrect "scrips" key with "scripts" in
the examples (fix the 'scrips' → 'scripts' typo) and update the Form Elements
documentation table to list the actual properties used in the JSON example:
document "element", "name", "label", and "items" (e.g. element: "dropDown") so
the table matches the payload shape shown in the sample scripts and the
ScriptResponse examples.
In `@src/lib/ScriptUtils.js`:
- Around line 98-101: The current construction of note using
JSON.stringify(response) in executeScript and executeScriptCallback can throw on
circular refs or BigInt; wrap the serialization in a try/catch: attempt
JSON.stringify(response) and on error fall back to String(response) (or a safe
custom replacer) to produce the note, then call showNote(note); update the code
paths that build the note (referencing the variables response, note and the
showNote call) so serialization failures do not cause the whole reporting to
fail.
🧹 Nitpick comments (1)
src/dashboard/Data/Browser/Browser.react.js (1)
2210-2241: Sentinel-property pattern for probe errors is fragile.The
.catch(error => ({ __probeError: error }))pattern on line 2215 converts a rejected promise into a resolved one carrying a magic property. If a Cloud Function ever returns an object with a__probeErrorkey, it would be misinterpreted as an error. Consider using a dedicated wrapper or a separate boolean flag instead.♻️ Suggested alternative using a structured result
- const probeResponse = await Parse.Cloud.run( + let probeResponse; + let probeError; + try { + probeResponse = await Parse.Cloud.run( script.cloudCodeFunction, { object: objects[0].toPointer() }, { useMasterKey: true } - ).catch(error => ({ __probeError: error })); + ); + } catch (error) { + probeError = error; + } - if (isFormResponse(probeResponse)) { + if (!probeError && isFormResponse(probeResponse)) { this.handleScriptModalResponse({ response: probeResponse, script, @@ ... this.setState(prevState => ({ processedScripts: prevState.processedScripts + 1, })); - if (probeResponse?.__probeError) { - const error = probeResponse.__probeError; + if (probeError) { + const error = probeError; const errorMessage = `Error running script "${script.title}" on "${objects[0].id}": ${error.message}`; ... - let totalErrorCount = probeResponse?.__probeError ? 1 : 0; + let totalErrorCount = probeError ? 1 : 0;
parseplatformorg
pushed a commit
that referenced
this pull request
Feb 10, 2026
# [8.5.0-alpha.7](8.5.0-alpha.6...8.5.0-alpha.7) (2026-02-10) ### Features * Add support for script execution invoking dashboard form for user input ([#3201](#3201)) ([159f99d](159f99d))
Contributor
|
🎉 This change has been released in version 8.5.0-alpha.7 |
parseplatformorg
pushed a commit
that referenced
this pull request
Feb 12, 2026
# [8.5.0](8.4.0...8.5.0) (2026-02-12) ### Bug Fixes * Auto-formatting not applied when Cloud Config parameter value is outdated and re-fetched from server ([#3182](#3182)) ([84eab36](84eab36)) * Clicking reload button in info panel may display fetched data in incorrect panel ([#3189](#3189)) ([b348ef5](b348ef5)) * Role linking in ACL fails with type error ([#3095](#3095)) ([2070d29](2070d29)) * Security migration from csurf to csrf-sync ([#3188](#3188)) ([a95d8a3](a95d8a3)) * View configuration dialog looses focus while typing and lacks syntax highlighting ([#3183](#3183)) ([715fe8d](715fe8d)) ### Features * Add keyboard shortcut to scroll info panels to top ([#3199](#3199)) ([7535626](7535626)) * Add option to reload all or only selected rows after invoking script ([#3200](#3200)) ([173b953](173b953)) * Add reload button to info panel on long loading time ([#3184](#3184)) ([3712d96](3712d96)) * Add support for script execution invoking dashboard form for user input ([#3201](#3201)) ([159f99d](159f99d))
Contributor
|
🎉 This change has been released in version 8.5.0 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request
Feature
Add support for script execution invoking dashboard form for user input.
Summary by CodeRabbit
New Features
Bug Fixes
Documentation