fix: Data browser export triggers confirmation dialog for navigating with selected rows

[mtrezza]

Summary by CodeRabbit

• Bug Fixes
  • Navigation prompts for selected rows are now suppressed during export operations, providing a cleaner user experience.

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

[parse-github-assistant]

🚀 Thanks for opening this pull request!

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR refactors the condition for displaying the SelectedRowsNavigationPrompt in Browser.react.js by replacing a direct length check with a precomputed selectionCount variable and adding an exporting state guard to suppress the prompt during export operations.

Changes

Cohort / File(s)	Change Summary
Navigation Prompt Control Flow src/dashboard/Data/Browser/Browser.react.js	Refactors SelectedRowsNavigationPrompt render condition to use precomputed selectionCount variable and add !this.state.exporting guard, preventing prompt display during export operations

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

• Verify selectionCount is properly defined and initialized
• Confirm this.state.exporting exists and is correctly managed
• Check that the additional guard does not introduce unintended side effects with existing selection workflows

Possibly related PRs

• feat: Warn when leaving data browser page with selected rows #2887 — Directly modifies the same SelectedRowsNavigationPrompt condition logic in Browser.react.js
• fix: Missing alert when changing data browser table data while rows are selected #2994 — Updates selected-rows navigation prompt guards and pass-throughs in the same Browser.react.js file
• fix: Warning dialog is shown after executing script on selected rows #2899 — Adjusts selection state and leave/confirmation prompt handling in Browser.react.js during refresh operations

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	No pull request description was provided. The required template sections including Issue Description, Approach, and TODOs are missing.	Add a complete description following the template: include the issue reference, describe the approach taken, and check off relevant TODOs before merging.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the specific fix: suppressing the navigation confirmation dialog during export operations when rows are selected.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

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

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 759cfac and 3145667.

📒 Files selected for processing (1)

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

🧰 Additional context used

🧠 Learnings (3)

📓 Common learnings

Learnt from: mtrezza
Repo: parse-community/parse-dashboard PR: 2957
File: src/dashboard/Data/Browser/BrowserTable.react.js:584-597
Timestamp: 2025-07-31T06:12:17.707Z
Learning: In Parse Dashboard's data browser selection logic (src/dashboard/Data/Browser/BrowserTable.react.js), the `selection['*']` pattern is used to handle global operations that pass `{ '*': true }` to indicate all items are selected, particularly for bulk operations like delete. This is not dead code but serves as compatibility layer for global operations that don't go through normal individual row selection workflows.

Learnt from: mtrezza
Repo: parse-community/parse-dashboard PR: 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.

📚 Learning: 2025-07-31T06:12:17.707Z

Learnt from: mtrezza
Repo: parse-community/parse-dashboard PR: 2957
File: src/dashboard/Data/Browser/BrowserTable.react.js:584-597
Timestamp: 2025-07-31T06:12:17.707Z
Learning: In Parse Dashboard's data browser selection logic (src/dashboard/Data/Browser/BrowserTable.react.js), the `selection['*']` pattern is used to handle global operations that pass `{ '*': true }` to indicate all items are selected, particularly for bulk operations like delete. This is not dead code but serves as compatibility layer for global operations that don't go through normal individual row selection workflows.

Applied to files:

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

📚 Learning: 2025-05-27T12:09:47.644Z

Learnt from: mtrezza
Repo: parse-community/parse-dashboard PR: 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.

Applied to files:

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

⏰ 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)

2768-2774: LGTM! The fix correctly suppresses the navigation prompt during export.

The addition of the !this.state.exporting guard prevents the navigation prompt from triggering when users export selected rows. The precomputed selectionCount variable also improves readability.

---

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

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

[parseplatformorg]

🎉 This change has been released in version 8.1.0-alpha.12

[parseplatformorg]

🎉 This change has been released in version 8.1.0