Skip to content

feat: add copy feedback to preferences sheet - #1022

Open
vedayeminedi wants to merge 1 commit into
imDarshanGK:mainfrom
vedayeminedi:issue-790-copy-feedback
Open

feat: add copy feedback to preferences sheet#1022
vedayeminedi wants to merge 1 commit into
imDarshanGK:mainfrom
vedayeminedi:issue-790-copy-feedback

Conversation

@vedayeminedi

Copy link
Copy Markdown

Linked issue

Closes #790

What this PR does

Adds explicit visual feedback when copying the configuration summary from the Preferences sheet.

Changes

  • Replaced the boolean copy state with a copyStatus state (idle, success, error).
  • Displays a success message ("✓ Copied!") after a successful copy operation.
  • Displays an error message ("⚠ Copy failed") if the clipboard operation fails.
  • Resets the feedback state after a short delay.
  • Added focused tests covering both successful and failed clipboard copy scenarios.

Type of change

  • ✨ New feature
  • 🐛 Bug fix
  • 💥 Breaking change
  • 📚 Documentation update

@vercel

vercel Bot commented Jul 24, 2026

Copy link
Copy Markdown

@vedayeminedi is attempting to deploy a commit to the Darshan's projects Team on Vercel.

A member of the Team first needs to authorize it.

@vedayeminedi

Copy link
Copy Markdown
Author

Hi @imDarshanGK, I verified the changes related to this PR by running the SettingsPanel test suite locally, and all tests passed. The failures shown in the full test suite appear to be from existing tests in Sidebar.test.jsx and UploadPanel.test.jsx, which are outside the scope of this PR. Please let me know if you'd like me to investigate anything further.

@imDarshanGK imDarshanGK added SSoC26 Part of Social Summer of Code 2026 Easy Beginner-friendly implementation work labels Jul 24, 2026

@imDarshanGK imDarshanGK left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vedayeminedi

Copy link
Copy Markdown
Author

Hi @imDarshanGK, I verified the frontend changes in this PR locally, and the SettingsPanel test suite passes successfully. This PR only modifies frontend/src/components/SettingsPanel.jsx and frontend/src/components/SettingsPanel.test.jsx. The failing CI check appears to be in the Backend (Python) workflow, which is outside the scope of these changes. Please let me know if you'd like me to investigate anything further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Easy Beginner-friendly implementation work SSoC26 Part of Social Summer of Code 2026

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add copy feedback to preferences sheet

2 participants