Skip to content

Remove UsernameCard from profile page - #6

Merged
holkexyz merged 1 commit into
mainfrom
fix/remove-username-card-from-profile
Mar 11, 2026
Merged

Remove UsernameCard from profile page#6
holkexyz merged 1 commit into
mainfrom
fix/remove-username-card-from-profile

Conversation

@holkexyz

Copy link
Copy Markdown
Member

Summary

  • Removes the UsernameCard component from the dashboard profile page
  • Removes the unused pdsUrl destructure from useAuth() and the UsernameCard dynamic import

One file changed, 4 lines removed.

@vercel

vercel Bot commented Mar 11, 2026

Copy link
Copy Markdown
Contributor

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

Project Deployment Actions Updated (UTC)
certified-app Ready Ready Preview, Comment Mar 11, 2026 6:37am

Request Review

@coderabbitai

coderabbitai Bot commented Mar 11, 2026

Copy link
Copy Markdown
ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Free

Run ID: 8220d68f-af3c-4cfa-9c0c-ad257b28ba21

📥 Commits

Reviewing files that changed from the base of the PR and between 8e10ade and 36bdd5c.

📒 Files selected for processing (1)
  • src/components/landing/home-client.tsx

📝 Walkthrough

Walkthrough

This pull request removes the unused UsernameCard component from the home client landing page. The change eliminates the dynamic import, the pdsUrl variable destructuring from the useAuth() hook, and the component invocation from the authenticated dashboard render flow.

Changes

Cohort / File(s) Summary
UsernameCard Removal
src/components/landing/home-client.tsx
Removed dynamic import and usage of UsernameCard component, dropped pdsUrl from useAuth() destructuring, and eliminated the component invocation from the dashboard render path.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

Poem

🐰 A card once danced in the dashboard's embrace,
But now it's cleared from this landing place,
The pdsUrl fades like morning dew,
Cleaner code—hopping forward anew! 🌱


Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

Comment @coderabbitai help to get the list of available commands and usage tips.

@holkexyz
holkexyz merged commit f1c8577 into main Mar 11, 2026
3 checks passed
hb-agent pushed a commit that referenced this pull request May 10, 2026
Round-2 reviewer C flagged the link-level analogue of round-1's
top-level forward-compat issue: the additional-links save loop
reconstructed each {url, label} from scratch, dropping any per-item
extras a future writer (CLI or feature) might add (e.g. verified,
addedAt). Each row now carries a `loadedRef` to the original record
item; the save spreads loadedRef under the new url/label, mirroring
the same pattern used for the top-level metadata builder. Cleared
labels still come off the wire because `label: undefined` is dropped
by JSON.stringify.

Same change adds a stable per-row id (round-2 reviewer A nit #4 / C
suggestion #2): inputs are now React-keyed by `row.id` instead of array
index, so removing a middle row no longer reuses DOM nodes / focus /
selection from a different row.

Smaller round-2 nits in the same diff:
- Trash button gains `disabled={isSaving}` for parity with Add link
  (B nit #4); adds disabled-style classes for visual feedback.
- Inline comment on the Type radio onChange documents that
  typeOtherText is intentionally preserved when toggling Other → preset
  (A nit #2). Save logic is unaffected.
- profile-client.tsx: the empty-state branch's redundant
  `editHref &&` guard was removed (B nit #6); converted the wrapping
  `(hasDetails || editHref) && <div>...` block to a clean ternary that
  TypeScript narrows correctly. Also reflowed indentation inside the
  Details `<dl>` after the ternary collapse.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant