fix: Context menu of header cell in info panel does not group related records by class name

[mtrezza]

New Pull Request Checklist

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

Summary by CodeRabbit

• Improvements

  • Reorganized the related records context menu in the data browser to display fields grouped by their parent class name, providing a more hierarchical and organized menu structure.

• Chores

  • Added a new npm script to manage termination of background processes during development.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[parse-github-assistant]

🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review.

[parseplatformorg]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new npm script browser-control:quit is added to terminate mongod, parse-server, and parse-dashboard processes. The related records context menu structure in DataBrowser.react.js is refactored to group fields hierarchically by class name instead of displaying them as standalone entries.

Changes

Cohort / File(s)	Summary
NPM Scripts Configuration package.json	Added browser-control:quit script to kill mongod, parse-server, and parse-dashboard processes via pkill commands. Minor formatting adjustment to browser-control:visible.
Related Records Menu Restructuring src/dashboard/Data/Browser/DataBrowser.react.js	Modified context menu generation to accumulate fields per class into a local array, then group them under a parent menu item labeled with the class name. Fields are sorted and nested as children rather than appearing as individual top-level entries.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• feat: Add getting related records to context menu of info panel header #3083: Modifies the same DataBrowser.react.js file to restructure the "related records" context menu with class-based grouping of fields.
• feat: Add context menu in data browser to get related records from String and Number fields #3118: Implements similar class-based field aggregation for the related records submenu in BrowserCell.react.js.
• fix: Info panel data not reloading when clicking refresh button in data browser #3027: Contains additional modifications to DataBrowser.react.js affecting different aspects of component functionality.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is incomplete. It only includes the checklist but omits the critical Issue Description, Approach, and TODOs sections required by the template.	Complete the missing template sections: add Issue Description with the issue reference, describe the Approach taken, and list any TODOs before merging.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: grouping related records by class name in the context menu of header cells in the info panel.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@package.json`:
- Line 151: Update the NPM script named "browser-control:quit" to ensure all
pkill commands run even if one fails: replace the chained "pkill -f mongod &&
pkill -f parse-server && pkill -f parse-dashboard" sequence with a form that
does not short-circuit on non-zero exit (e.g., use '; true' after each pkill or
use '|| true' for each command) so each pkill (for mongod, parse-server,
parse-dashboard) is attempted regardless of previous failures.

[parseplatformorg]

🎉 This change has been released in version 8.3.0-alpha.5