fix: Whitelist app config fields sent to the client

[dblythy]

Closes #1517

Problem

/parse-dashboard-config.json (Parse-Dashboard/app.js) sends a shallow copy of each app object to the browser:

const apps = config.apps.map((app) => Object.assign({}, app)); // make a copy

Many users reuse their Parse Server config as the dashboard app config, so apps[] often carries server-only fields. This has two consequences:

1. Crash: a filesAdapter instance holds circular references (e.g. a Mongo topology), so res.json throws TypeError: Converting circular structure to JSON and the whole dashboard fails to load with a "Server Error".
2. Leak: every server-only field the user pasted (including readOnlyMasterKey, databaseURI) is shipped to the browser even though the client never reads them.

Fix

Send only a whitelist of the per-app fields the client actually consumes. The whitelist is the union of what src/lib/ParseApp.js destructures, the raw infoPanel read directly in Browser.react.js, and the documented app options in the README. The projection is applied at send time (after the existing read-only masterKey resolution, which still needs readOnlyMasterKey/masterKeyTtl), so those server-only fields are used for shaping but never sent.

This fixes the circular-JSON crash and stops leaking server-only fields. readOnlyMasterKey and masterKeyTtl are now stripped from the payload (intentional tightening; the client never read them).

Note: the whitelist includes both apiKey and fileKey because the README documents the option as fileKey while ParseApp.js destructures apiKey. That naming mismatch is pre-existing and left as-is here.

Verification

Added src/lib/tests/dashboardConfig.test.js (red→green against the real app.js server): with a circular filesAdapter in the config, it asserts the endpoint responds 200, includes the whitelisted client fields, and omits filesAdapter/databaseURI/readOnlyMasterKey/masterKeyTtl.

Runtime, same app config with a circular filesAdapter:

Before: GET /parse-dashboard-config.json returns 500 (Converting circular structure to JSON), and the dashboard fails to load:

After: the endpoint returns 200 with only whitelisted fields, and the dashboard loads:

(The "Server not reachable" note in the after image is only because no Parse Server backend was running for this QA; it is unrelated to the config fix, which is what loaded the app.)

[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.

Tip

• Keep pull requests small. Large PRs will be rejected. Break complex features into smaller, incremental PRs.
• Use Test Driven Development. Write failing tests before implementing functionality. Ensure tests pass.
• Group code into logical blocks. Add a short comment before each block to explain its purpose.
• We offer conceptual guidance. Coding is up to you. PRs must be merge-ready for human review.
• Our review focuses on concept, not quality. PRs with code issues will be rejected. Use an AI agent.
• Human review time is precious. Avoid review ping-pong. Inspect and test your AI-generated code.

Note

Please respond to review comments from AI agents just like you would to comments from a human reviewer. Let the reviewer resolve their own comments, unless they have reviewed and accepted your commit, or agreed with your explanation for why the feedback was incorrect.

Caution

Pull requests must be written using an AI agent with human supervision. Pull requests written entirely by a human will likely be rejected, because of lower code quality, higher review effort and the higher risk of introducing bugs. Please note that AI review comments on this pull request alone do not satisfy this requirement. Our CI and AI review are safeguards, not development tools. If many issues are flagged, rethink your development approach. Invest more effort in planning and design rather than using review cycles to fix low-quality code.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 36 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 25967627-03a9-4a4c-a672-dfb0eb788214

📥 Commits

Reviewing files that changed from the base of the PR and between 9db24be and 2359384.

📒 Files selected for processing (2)

• Parse-Dashboard/app.js
• src/lib/tests/dashboardConfig.test.js

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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