chore: Remove un-used UI components

[MichaelUnkey]

What does this PR do?

Fixes # (issue)

If there is not an issue for this, please create one first. This is used to tracking purposes and also helps us understand why this PR exists

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Chore (refactoring code, technical debt, workflow improvements)
• Enhancement (small improvements)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How should this be tested?

• Dashboard still builds with no errors
• Teams page still works as it should. Small changes were made to remove last pageHeader being used in dashboard.

Checklist

Required

• Filled out the "How to test" section in this PR
• Read Contributing Guide
• Self-reviewed my own code
• Commented on my code in hard-to-understand areas
• Ran pnpm build
• Ran pnpm fmt
• Ran make fmt on /go directory
• Checked for warnings, there are none
• Removed all console.logs
• Merged the latest changes from main onto my branch with git pull origin main
• My changes don't cause any responsiveness issues

Appreciated

• If a UI change was made: Added a screen recording or screenshots to this PR
• Updated the Unkey Docs if changes were necessary

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5a52437

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

📝 Walkthrough

Walkthrough

Removes many dashboard UI components and utilities (PageHeader, Navbar, Confirm, chart and LLM-search subsystems, several UI atoms). Replaces inline Confirm with a ConfirmPopover flow in members UI and removes some header/submenu renderings in settings and integrations pages.

Changes

Cohort / File(s)	Summary
Settings — header/action removals apps/dashboard/app/(app)/[workspaceSlug]/settings/team/client.tsx, apps/dashboard/app/(app)/[workspaceSlug]/settings/vercel/client.tsx, apps/dashboard/app/(app)/[workspaceSlug]/settings/vercel/page.tsx	Removed PageHeader usage and related header actions; vercel/page.tsx also removes SubMenu rendering. Layout/top-of-list header content omitted.
Settings — members: confirm → popover apps/dashboard/app/(app)/[workspaceSlug]/settings/team/members.tsx	Replaced inline Confirm flow with a ConfirmPopover implementation; adds local state (isConfirmPopoverOpen, currentMembership, anchorEl) and per-row delete button that opens the popover and calls the removeMember mutation on confirm.
Integrations callback UI apps/dashboard/app/integrations/vercel/callback/client.tsx	Removed PageHeader import/render; WorkspaceSwitcher import commented out. Form and project selection remain.
Deleted chart utilities apps/dashboard/components/dashboard/charts.tsx	Deleted file — removes useColors hook, color types, and chart components: AreaChart, LineChart, ColumnChart, StackedColumnChart, StackedBarChart and associated formatting/theme logic.
Deleted core dashboard components apps/dashboard/components/dashboard/page-header.tsx, apps/dashboard/components/dashboard/navbar.tsx, apps/dashboard/components/dashboard/confirm.tsx	Deleted PageHeader, Navbar (and NavItem), and Confirm component files and their exported types/props.
Removed Logs LLM-search subsystem apps/dashboard/components/logs/llm-search/index.tsx, apps/dashboard/components/logs/llm-search/components/search-icon.tsx, .../search-input.tsx, .../search-actions.tsx, .../search-example-tooltip.tsx, apps/dashboard/components/logs/llm-search/hooks/use-search-strategy.ts, apps/dashboard/components/logs/llm-search/hooks/use-search-strategy.test.tsx	Entire LLM-assisted search feature removed: LogsLLMSearch component, subcomponents (SearchIcon, SearchInput, SearchActions, SearchExampleTooltip), the useSearchStrategy hook, and its tests.
Deleted small UI atoms apps/dashboard/components/ui/calendar.tsx, apps/dashboard/components/ui/code.tsx, apps/dashboard/components/ui/metric.tsx, apps/dashboard/components/ui/shiny-text.tsx	Removed Calendar, Code, Metric, and AnimatedShinyText components and their exported types/variants.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

• Areas needing extra attention:
  • Search/LLM subsystem removals: ensure no remaining imports or references across the codebase.
  • Chart and UI atom deletions: verify usages (pages, dashboards, docs) and update imports.
  • members.tsx Confirm → ConfirmPopover migration: confirm anchor/ref handling, mutation/error paths, and accessibility/focus behavior.
  • PageHeader/Navbar/Confirm deletions: search for residual usages that could cause compile/runtime errors.

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: removing unused UI components. It is clear, concise, and directly related to the changeset.
Description check	✅ Passed	The PR description follows the template structure, includes the required sections (What does this PR do, Type of change, How should this be tested, Checklist), and provides testing instructions and completion of most required checklist items.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch remove-un-used-ui-components

---

📜 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 f87e617 and fd3f007.

📒 Files selected for processing (1)

• apps/dashboard/app/(app)/[workspaceSlug]/settings/team/members.tsx (4 hunks)

🧰 Additional context used

🧠 Learnings (2)

📚 Learning: 2024-12-03T14:07:45.173Z

Learnt from: ogzhanolguncu
Repo: unkeyed/unkey PR: 2143
File: apps/dashboard/components/ui/group-button.tsx:21-31
Timestamp: 2024-12-03T14:07:45.173Z
Learning: In the `ButtonGroup` component (`apps/dashboard/components/ui/group-button.tsx`), avoid suggesting the use of `role="group"` in ARIA attributes.

Applied to files:

• apps/dashboard/app/(app)/[workspaceSlug]/settings/team/members.tsx

📚 Learning: 2025-01-07T19:55:33.055Z

Learnt from: chronark
Repo: unkeyed/unkey PR: 2792
File: apps/dashboard/app/(app)/settings/user/update-user-email.tsx:76-78
Timestamp: 2025-01-07T19:55:33.055Z
Learning: In the Unkey codebase, the Empty component can be used as a container for loading states, as demonstrated in the UpdateUserEmail component where it wraps the Loading component.

Applied to files:

• apps/dashboard/app/(app)/[workspaceSlug]/settings/team/members.tsx

🧬 Code graph analysis (1)

apps/dashboard/app/(app)/[workspaceSlug]/settings/team/members.tsx (3)

apps/dashboard/lib/auth/types.ts (1)

• Membership (43-51)

internal/ui/src/components/dialog/confirmation-popover.tsx (1)

• ConfirmPopover (53-115)

apps/dashboard/app/(app)/[workspaceSlug]/projects/[projectId]/details/active-deployment-card/git-avatar.tsx (1)

• Avatar (11-30)

⏰ 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: Test Dashboard / Test Dashboard

🔇 Additional comments (3)

apps/dashboard/app/(app)/[workspaceSlug]/settings/team/members.tsx (3)

26-34: Previous shared-ref issue correctly resolved.

The fix properly addresses the earlier bug where all Remove buttons shared a single ref. Now each click captures the specific button via event.currentTarget (line 59) and stores it in anchorEl state, ensuring the popover anchors to the clicked button. The useMemo pattern (line 34) correctly wraps the state value as a ref-like object for PopoverAnchor.

Also applies to: 55-62

---

76-97: ConfirmPopover integration looks good.

The conditional rendering check (lines 76-77) ensures both the membership and anchor element exist before showing the popover. The onConfirm handler correctly invokes the mutation with proper parameters and error handling.

Note: The console.error on line 93 is fine—it's for error logging, distinct from debug console.log statements mentioned in the PR checklist.

---

107-154: Table rendering and remove action correctly implemented.

The membership iteration (line 107) passes the full object to the handler, eliminating the unnecessary id lookup from the previous implementation. The Remove button's onClick (line 146) cleanly delegates to handleDeleteButtonClick, which manages the popover state.

---

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
dashboard	Ready	Preview	Comment	Dec 5, 2025 7:36pm

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
engineering	Ignored	Preview		Dec 5, 2025 7:36pm

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (4)

apps/dashboard/app/integrations/vercel/callback/client.tsx (1)

23-23: Consider deleting the commented‑out WorkspaceSwitcher import

Given this PR’s goal of cleaning up unused UI components, it’d be more consistent to either fully remove this import or turn it into an explicit // TODO: note if you plan to reintroduce it. As-is, it’s just dead/commented code adding noise.

apps/dashboard/app/(app)/[workspaceSlug]/settings/team/client.tsx (1)

85-102: Consider removing the unnecessary wrapper div and redundant key props for cleaner code.

The wrapping <div> around the Select component (line 87) serves no styling or structural purpose and can be removed. Additionally, the key props on the Select and InviteButton components (lines 88, 100) are redundant since these are single instances and not part of a list. Removing them would simplify the code:

 {isAdmin ? (
   <div className="flex flex-row justify-end w-full gap-4">
-    <div>
-      <Select key="tab-select" value={tab} onValueChange={(value: Tab) => setTab(value)}>
+      <Select value={tab} onValueChange={(value: Tab) => setTab(value)}>
         <SelectTrigger className="w-[180px]">
           <SelectValue />
         </SelectTrigger>
         <SelectContent>
           <SelectGroup>
             <SelectItem value="members">Members</SelectItem>
             <SelectItem value="invitations">Invitations</SelectItem>
           </SelectGroup>
         </SelectContent>
       </Select>
-    </div>
-    <InviteButton key="invite-button" user={user} organization={organization} />
+    <InviteButton user={user} organization={organization} />
   </div>
 ) : null}

apps/dashboard/app/(app)/[workspaceSlug]/settings/team/members.tsx (2)

72-93: Consider clearing selection/closing the popover after a successful removal

onConfirm performs the mutation but never resets currentMembership or explicitly closes the controlled popover. Depending on ConfirmPopover’s internals this may still work, but keeping local state in sync makes the component more predictable and avoids stale selection.

You could reset on success:

           onConfirm={async () => {
             try {
               await removeMember.mutateAsync({
                 orgId: organization.id,
                 membershipId: currentMembership.id,
               });
+              setIsConfirmPopoverOpen(false);
+              setCurrentMembership(null);
             } catch (error) {
               console.error("Error removing member:", error);
             }
           }}

If ConfirmPopover already calls onOpenChange(false) on confirm, this will just be redundant but harmless and keeps currentMembership consistent with the UI.

---

97-100: Tidy the JSX comment in the header cell

Minor nit: {/*/ empty */} is slightly odd to read; it works, but the extra slash can confuse future readers. Consider simplifying to a standard JSX comment:

-            <TableHead>{/*/ empty */}</TableHead>
+            <TableHead>{/* empty */}</TableHead>

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fa48d4c and 085531b.

📒 Files selected for processing (22)

• apps/dashboard/app/(app)/[workspaceSlug]/settings/team/client.tsx (1 hunks)
• apps/dashboard/app/(app)/[workspaceSlug]/settings/team/members.tsx (5 hunks)
• apps/dashboard/app/(app)/[workspaceSlug]/settings/vercel/client.tsx (0 hunks)
• apps/dashboard/app/(app)/[workspaceSlug]/settings/vercel/page.tsx (0 hunks)
• apps/dashboard/app/integrations/vercel/callback/client.tsx (1 hunks)
• apps/dashboard/components/dashboard/charts.tsx (0 hunks)
• apps/dashboard/components/dashboard/confirm.tsx (0 hunks)
• apps/dashboard/components/dashboard/navbar.tsx (0 hunks)
• apps/dashboard/components/dashboard/page-header.tsx (0 hunks)
• apps/dashboard/components/dashboard/root-key-table/index.tsx (0 hunks)
• apps/dashboard/components/dashboard/root-key-table/table.tsx (0 hunks)
• apps/dashboard/components/logs/llm-search/components/search-actions.tsx (0 hunks)
• apps/dashboard/components/logs/llm-search/components/search-example-tooltip.tsx (0 hunks)
• apps/dashboard/components/logs/llm-search/components/search-icon.tsx (0 hunks)
• apps/dashboard/components/logs/llm-search/components/search-input.tsx (0 hunks)
• apps/dashboard/components/logs/llm-search/hooks/use-search-strategy.test.tsx (0 hunks)
• apps/dashboard/components/logs/llm-search/hooks/use-search-strategy.ts (0 hunks)
• apps/dashboard/components/logs/llm-search/index.tsx (0 hunks)
• apps/dashboard/components/ui/calendar.tsx (0 hunks)
• apps/dashboard/components/ui/code.tsx (0 hunks)
• apps/dashboard/components/ui/metric.tsx (0 hunks)
• apps/dashboard/components/ui/shiny-text.tsx (0 hunks)

💤 Files with no reviewable changes (19)

• apps/dashboard/components/logs/llm-search/hooks/use-search-strategy.ts
• apps/dashboard/components/logs/llm-search/components/search-actions.tsx
• apps/dashboard/components/dashboard/page-header.tsx
• apps/dashboard/app/(app)/[workspaceSlug]/settings/vercel/client.tsx
• apps/dashboard/components/dashboard/confirm.tsx
• apps/dashboard/components/ui/shiny-text.tsx
• apps/dashboard/components/ui/code.tsx
• apps/dashboard/components/dashboard/navbar.tsx
• apps/dashboard/components/ui/calendar.tsx
• apps/dashboard/components/logs/llm-search/components/search-example-tooltip.tsx
• apps/dashboard/app/(app)/[workspaceSlug]/settings/vercel/page.tsx
• apps/dashboard/components/dashboard/root-key-table/index.tsx
• apps/dashboard/components/logs/llm-search/components/search-input.tsx
• apps/dashboard/components/logs/llm-search/index.tsx
• apps/dashboard/components/dashboard/root-key-table/table.tsx
• apps/dashboard/components/logs/llm-search/hooks/use-search-strategy.test.tsx
• apps/dashboard/components/logs/llm-search/components/search-icon.tsx
• apps/dashboard/components/dashboard/charts.tsx
• apps/dashboard/components/ui/metric.tsx

🧰 Additional context used

🧠 Learnings (7)

📚 Learning: 2024-10-04T17:27:09.821Z

Learnt from: chronark
Repo: unkeyed/unkey PR: 2146
File: apps/dashboard/app/(app)/apis/[apiId]/settings/default-prefix.tsx:74-75
Timestamp: 2024-10-04T17:27:09.821Z
Learning: In `apps/dashboard/app/(app)/apis/[apiId]/settings/default-prefix.tsx`, the hidden `<input>` elements for `workspaceId` and `keyAuthId` work correctly without being registered with React Hook Form.

Applied to files:

• apps/dashboard/app/integrations/vercel/callback/client.tsx
• apps/dashboard/app/(app)/[workspaceSlug]/settings/team/client.tsx

📚 Learning: 2025-07-28T19:42:37.047Z

Learnt from: mcstepp
Repo: unkeyed/unkey PR: 3662
File: apps/dashboard/app/(app)/projects/page.tsx:74-81
Timestamp: 2025-07-28T19:42:37.047Z
Learning: In apps/dashboard/app/(app)/projects/page.tsx, the user mcstepp prefers to keep placeholder functions like generateSlug inline during POC/demonstration phases rather than extracting them to utility modules, with plans to refactor later when the feature matures beyond the proof-of-concept stage.

Applied to files:

• apps/dashboard/app/integrations/vercel/callback/client.tsx
• apps/dashboard/app/(app)/[workspaceSlug]/settings/team/client.tsx

📚 Learning: 2025-07-28T20:38:53.244Z

Learnt from: mcstepp
Repo: unkeyed/unkey PR: 3662
File: apps/dashboard/app/(app)/projects/[projectId]/diff/[...compare]/components/client.tsx:322-341
Timestamp: 2025-07-28T20:38:53.244Z
Learning: In apps/dashboard/app/(app)/projects/[projectId]/diff/[...compare]/components/client.tsx, mcstepp prefers to keep hardcoded endpoint logic in the getDiffType function during POC phases for demonstrating diff functionality, rather than implementing a generic diff algorithm. This follows the pattern of keeping simplified implementations for demonstration purposes.

Applied to files:

• apps/dashboard/app/integrations/vercel/callback/client.tsx

📚 Learning: 2025-08-18T10:28:47.391Z

Learnt from: ogzhanolguncu
Repo: unkeyed/unkey PR: 3797
File: apps/dashboard/app/(app)/projects/[projectId]/deployments/components/control-cloud/index.tsx:1-4
Timestamp: 2025-08-18T10:28:47.391Z
Learning: In Next.js App Router, components that use React hooks don't need their own "use client" directive if they are rendered within a client component that already has the directive. The client boundary propagates to child components.

Applied to files:

• apps/dashboard/app/integrations/vercel/callback/client.tsx
• apps/dashboard/app/(app)/[workspaceSlug]/settings/team/client.tsx

📚 Learning: 2025-09-23T17:39:59.820Z

Learnt from: perkinsjr
Repo: unkeyed/unkey PR: 4009
File: apps/dashboard/app/(app)/[workspace]/apis/[apiId]/_overview/components/table/components/override-indicator.tsx:88-97
Timestamp: 2025-09-23T17:39:59.820Z
Learning: The useWorkspaceNavigation hook in the Unkey dashboard guarantees that a workspace exists. If no workspace is found, the hook redirects the user to create a new workspace. Users cannot be logged in without a workspace, and new users must create one to continue. Therefore, workspace will never be null when using this hook.

Applied to files:

• apps/dashboard/app/integrations/vercel/callback/client.tsx
• apps/dashboard/app/(app)/[workspaceSlug]/settings/team/client.tsx

📚 Learning: 2025-05-15T16:26:08.666Z

Learnt from: ogzhanolguncu
Repo: unkeyed/unkey PR: 3242
File: apps/dashboard/app/(app)/apis/[apiId]/_overview/components/table/components/override-indicator.tsx:50-65
Timestamp: 2025-05-15T16:26:08.666Z
Learning: In the Unkey dashboard, Next.js router (router.push) should be used for client-side navigation instead of window.location.href to preserve client state and enable smoother transitions between pages.

Applied to files:

• apps/dashboard/app/integrations/vercel/callback/client.tsx

📚 Learning: 2025-09-22T18:44:56.279Z

Learnt from: perkinsjr
Repo: unkeyed/unkey PR: 4009
File: apps/dashboard/app/(app)/[workspace]/apis/[apiId]/_overview/components/table/components/log-details/index.tsx:4-5
Timestamp: 2025-09-22T18:44:56.279Z
Learning: In the Unkey dashboard, the workspace hook (useWorkspace) provides security validation by checking database access and user authorization to the workspace, with 10-minute caching for performance. Using URL params (useParams) for workspace slug would bypass this security validation and allow unauthorized access attempts. Always use the workspace hook for workspace-scoped navigation and handle loading states properly rather than switching to URL parameters.

Applied to files:

• apps/dashboard/app/integrations/vercel/callback/client.tsx

🧬 Code graph analysis (1)

apps/dashboard/app/(app)/[workspaceSlug]/settings/team/client.tsx (1)

internal/ui/src/components/form/select.tsx (6)

• Select (171-171)
• SelectTrigger (174-174)
• SelectValue (173-173)
• SelectContent (175-175)
• SelectGroup (172-172)
• SelectItem (177-177)

⏰ 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: Test Dashboard / Test Dashboard

[graphite-app]

[graphite-app]

Graphite Automations

"Post a GIF when PR approved" took an action on this PR • (12/05/25)

1 gif was posted to this PR based on Andreas Thomas's automation.