You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
refactor: Clean up unused clipboard handler and dead code in ResultDashboard #230
In src/features/comparison/components/result-dashboard.tsx, clipboard copying logic is defined but never rendered.
Motivation
Unused hooks and dead functions clutter the component and confuse contributors. We should either wire this up to an active button or clean up the unused state.
Tasks
Inspect result-dashboard.tsx lines 65 and 113-128 (useClipboardCopy and handleCopy).
Either:
Option A (Recommended): Add a small 'Copy Raw JSON' / 'Debug Data' action button or dropdown item that invokes handleCopy for developers needing raw payload data.
Option B: Remove the unused handleCopy, copied, and unused icon imports (Check, Copy).
Run pnpm lint and npx tsc --noEmit to ensure clean code.
Tip
🚀 Want to contribute?
Comment assign me to be automatically assigned to this issue via our GitHub Actions bot. Happy coding! ✨
Verified on current main: handleCopy (result-dashboard.tsx) is wired to a rendered secondary Copy button — onClick={handleCopy} with the copied state, Check/Copy icons and aria-labels — next to the Share and Copy-markdown buttons, so both it and the useClipboardCopy instance at line 66 are in use. This looks already implemented (Option A); sharing in case it helps you close the issue.
Activity
rahul05ranjan commentedon Oct 23, 2026
assign me
github-actions commentedon Oct 23, 2026
🎉 Issue assigned to @rahul05ranjan! Happy coding!
rahul05ranjan commentedon Oct 23, 2026
Verified on current main:
handleCopy(result-dashboard.tsx) is wired to a rendered secondary Copy button —onClick={handleCopy}with thecopiedstate,Check/Copyicons and aria-labels — next to the Share and Copy-markdown buttons, so both it and theuseClipboardCopyinstance at line 66 are in use. This looks already implemented (Option A); sharing in case it helps you close the issue.