feat: Warn when leaving data browser page with selected rows

[mtrezza]

Summary

• add a SelectedRowsNavigationPrompt component
• block navigation when rows are selected

Testing

• npm test
• npm run lint

---

https://chatgpt.com/codex/tasks/task_e_686f75526498832d96af43a2b0cb2709

Summary by CodeRabbit

• New Features

  • Users are now prompted with a confirmation dialog if they attempt to navigate away or close the browser tab while rows are selected in the data browser, helping prevent accidental loss of selections.

• Bug Fixes

  • Improved checkbox behavior in the data browser to ensure selection states are handled more reliably.

[parse-github-assistant]

The label codex cannot be used here.

[parse-github-assistant]

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

[coderabbitai]

Warning

Rate limit exceeded

@mtrezza has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 17 minutes and 4 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 982523c and f74ba30.

📒 Files selected for processing (1)

• src/dashboard/Data/Browser/Browser.react.js (3 hunks)

📝 Walkthrough

Walkthrough

A new React component, SelectedRowsNavigationPrompt, was introduced in the data browser to intercept navigation or page unloads when rows are selected, prompting the user for confirmation. Additionally, a minor update was made to the row selection checkbox logic to ensure its checked state is always a boolean.

Changes

File(s)	Change Summary
src/dashboard/Data/Browser/Browser.react.js	Added usePrompt hook and SelectedRowsNavigationPrompt component to block navigation/unload when rows are selected; integrated into Browser render logic.
src/components/BrowserRow/BrowserRow.react.js	Modified checkbox checked attribute to explicitly coerce selection values to boolean.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant BrowserComponent
    participant SelectedRowsNavigationPrompt
    participant ReactRouter
    participant Window

    User->>BrowserComponent: Selects one or more rows
    BrowserComponent->>SelectedRowsNavigationPrompt: Renders with when=true
    User->>ReactRouter: Attempts navigation (e.g., clicks link)
    ReactRouter->>SelectedRowsNavigationPrompt: Triggers location change
    SelectedRowsNavigationPrompt->>User: Displays window.confirm dialog
    alt User confirms navigation
        SelectedRowsNavigationPrompt->>ReactRouter: Allows navigation
    else User cancels navigation
        SelectedRowsNavigationPrompt->>ReactRouter: Navigates back to previous location
    end
    User->>Window: Attempts to close or reload tab
    Window->>SelectedRowsNavigationPrompt: Triggers beforeunload event
    SelectedRowsNavigationPrompt->>User: Displays confirmation dialog

Loading

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai auto-generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[parse-github-assistant]

🚀 Thanks for opening this pull request!

[parseplatformorg]

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

✅ security/snyk check is complete. No issues have been found. (View Details)

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1c94668 and d30aaf9.

📒 Files selected for processing (1)

• src/dashboard/Data/Browser/Browser.react.js (2 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: mtrezza
PR: parse-community/parse-dashboard#2828
File: src/dashboard/Data/Browser/Browser.react.js:1605-1607
Timestamp: 2025-05-27T12:09:47.644Z
Learning: In script execution dialogs in Parse Dashboard (specifically the `confirmExecuteScriptRows` method in `src/dashboard/Data/Browser/Browser.react.js`), individual `setState` calls to update `processedScripts` counter should be kept as-is rather than batched, because this provides real-time progress feedback to users in the dialog UI.

src/dashboard/Data/Browser/Browser.react.js (2)

Learnt from: mtrezza
PR: parse-community/parse-dashboard#2828
File: src/dashboard/Data/Browser/Browser.react.js:1605-1607
Timestamp: 2025-05-27T12:09:47.644Z
Learning: In script execution dialogs in Parse Dashboard (specifically the `confirmExecuteScriptRows` method in `src/dashboard/Data/Browser/Browser.react.js`), individual `setState` calls to update `processedScripts` counter should be kept as-is rather than batched, because this provides real-time progress feedback to users in the dialog UI.

Learnt from: mtrezza
PR: parse-community/parse-dashboard#2769
File: src/lib/ClassPreferences.js:26-26
Timestamp: 2025-05-02T11:55:52.809Z
Learning: Preference reads and writes in the ClassPreferences.js module are expected to be infrequent operations, so optimizing for performance (like caching) is unnecessary in this context.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Node 18
• GitHub Check: Docker linux/amd64

🔇 Additional comments (1)

src/dashboard/Data/Browser/Browser.react.js (1)

2468-2470: LGTM! Component integration is correct.

The component is properly integrated with the correct condition to check for selected rows. The placement in the render method is appropriate.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1388477 and 7170bff.

📒 Files selected for processing (4)

• src/components/BrowserRow/BrowserRow.react.js (1 hunks)
• src/dashboard/Dashboard.js (3 hunks)
• src/dashboard/Data/Browser/Browser.react.js (2 hunks)
• src/lib/history.js (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• src/lib/history.js

🚧 Files skipped from review as they are similar to previous changes (1)

• src/dashboard/Data/Browser/Browser.react.js

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: mtrezza
PR: parse-community/parse-dashboard#2828
File: src/dashboard/Data/Browser/Browser.react.js:1605-1607
Timestamp: 2025-05-27T12:09:47.644Z
Learning: In script execution dialogs in Parse Dashboard (specifically the `confirmExecuteScriptRows` method in `src/dashboard/Data/Browser/Browser.react.js`), individual `setState` calls to update `processedScripts` counter should be kept as-is rather than batched, because this provides real-time progress feedback to users in the dialog UI.

🧬 Code Graph Analysis (1)

src/dashboard/Dashboard.js (1)

src/lib/history.js (1)

• history (3-3)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Docker linux/amd64

🔇 Additional comments (2)

src/components/BrowserRow/BrowserRow.react.js (1)

95-95: Good defensive programming practice!

Explicitly coercing the selection values to boolean ensures the checked attribute receives a strict boolean value, preventing potential issues with truthy non-boolean values.

src/dashboard/Dashboard.js (1)

315-327: Navigation blocking integration verified

The custom history (created in src/lib/history.js) is correctly passed into HistoryRouter, and history.block is implemented in src/dashboard/Data/Browser/Browser.react.js with the SelectedRowsNavigationPrompt logic. No further changes required.

[parseplatformorg]

🎉 This change has been released in version 7.3.0-alpha.10