fix: Invalid clipboard content for multi-cell copy in data browser

[mtrezza]

Summary

• normalize formatting when copying multiple cells from the data browser
• support GeoPoint and Date fields with same output as single-cell copy

Testing

• npm run lint
• npm test

---

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

Summary by CodeRabbit

• New Features

  • Improved the formatting of copied data from the data browser, ensuring values are consistently and clearly represented based on their type when using copy (Ctrl/Cmd + C).

• Enhancements

  • Copied values such as dates, files, booleans, and special types are now more readable and user-friendly.

[parse-github-assistant]

🚀 Thanks for opening this pull request!

[parse-github-assistant]

The label codex cannot be used here.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new helper function, formatValueForCopy, is introduced to standardize how different data types are converted to string representations for clipboard copying. The keyboard event handler for copying multiple selected cells now utilizes this function, ensuring that each cell's value is formatted appropriately based on its type before being copied.

Changes

File(s)	Change Summary
src/dashboard/Data/Browser/DataBrowser.react.js	Added formatValueForCopy for type-based value formatting; updated copy event handler to use this function for clipboard operations.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant DataBrowser
    participant formatValueForCopy

    User->>DataBrowser: Presses Ctrl/Cmd + C (copy)
    DataBrowser->>formatValueForCopy: For each selected cell, call with (value, type)
    formatValueForCopy-->>DataBrowser: Returns formatted string
    DataBrowser->>User: Clipboard updated with formatted data

Loading

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

npm error code ERR_SSL_WRONG_VERSION_NUMBER
npm error errno ERR_SSL_WRONG_VERSION_NUMBER
npm error request to https://10.0.0.28:4873/npm/-/npm-10.9.2.tgz failed, reason: C0EC11F0297F0000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:354:
npm error
npm error A complete log of this run can be found in: /.npm/_logs/2025-07-09T15_07_03_715Z-debug-0.log

---

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.

[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: 0

🧹 Nitpick comments (1)

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

37-37: Apply optional chaining for safer property access.

The static analysis tool correctly identifies an opportunity to use optional chaining for cleaner and safer code.

Apply this diff to use optional chaining:

-    case 'Date':
-      if (value && value.iso) {
-        value = new Date(value.iso);
-      } else if (typeof value === 'string') {
+    case 'Date':
+      if (value?.iso) {
+        value = new Date(value.iso);
+      } else if (typeof value === 'string') {

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 506f934 and b294644.

📒 Files selected for processing (1)

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

🧰 Additional context used

🪛 Biome (1.9.4)

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

[error] 37-37: Change to an optional chain.

Unsafe fix: Change to an optional chain.

(lint/complexity/useOptionalChain)

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

src/dashboard/Data/Browser/DataBrowser.react.js (4)

13-14: LGTM: New imports support clipboard formatting functionality.

The imports are appropriately used in the new formatValueForCopy function for handling Date and File types.

---

350-350: LGTM: Correct type determination for clipboard formatting.

The logic correctly determines the field type, with appropriate fallback to 'String' for the special case of objectId.

---

359-359: LGTM: Proper integration of the new formatting function.

The replacement of direct value pushing with formatValueForCopy ensures consistent formatting across all data types during multi-cell copy operations.

---

23-62: Fix missing return statements in switch cases.

The implementation correctly handles various data types, but there are missing return statements in the switch cases that will cause unintended fallthrough behavior.

Apply this diff to fix the missing return statements:

 case 'GeoPoint':
   if (value && value.latitude !== undefined && value.longitude !== undefined) {
     return `(${value.latitude}, ${value.longitude})`;
   }
-  break;
+  return JSON.stringify(value);
 case 'Date':
   if (value && value.iso) {
     value = new Date(value.iso);
   } else if (typeof value === 'string') {
     value = new Date(value);
   }
   if (value instanceof Date && !isNaN(value)) {
     return dateStringUTC(value);
   }
-  break;
+  return String(value);
 case 'File':
   if (value && typeof value.url === 'function') {
     return getFileName(value);
   }
-  break;
+  return String(value);

Likely an incorrect or invalid review comment.

[parseplatformorg]

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