fix(frontend): not hoverable projects in context switcher

[jog1t]

No description provided.

[railway-app]

🚅 Deployed to the rivet-pr-3791 environment in rivet-frontend

Service	Status	Web	Updated (UTC)
frontend-cloud-prod	✅ Success (View Logs)	Web	Jan 8, 2026 at 2:01 am
frontend-inspector	✅ Success (View Logs)	Web	Jan 8, 2026 at 2:01 am
frontend-cloud-staging	✅ Success (View Logs)	Web	Jan 8, 2026 at 2:01 am
website	✅ Success (View Logs)	Web	Jan 8, 2026 at 1:58 am

[jog1t]

• fix(frontend): not hoverable projects in context switcher #3791 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[claude]

PR Review

Summary

This PR fixes the issue where projects in the context switcher weren't hoverable. The root cause was that PrefetchedProjectListItem wasn't forwarding the onHover and onSelect props to ProjectListItem.

---

✅ Code Quality & Best Practices

Good:

• Root cause fix is correct: The main issue (missing prop forwarding in PrefetchedProjectListItem) is properly addressed using the spread operator ({...props})
• Defensive programming: Added null check for parentRect in safe-hover.tsx:19 prevents potential runtime errors
• Code consistency: Type import style change (import type { Project }) aligns with TypeScript best practices
• Minor optimization: Destructuring top and bottom in safe-hover.tsx:21 reduces method calls

Suggestions:

• The + 5 offset added in safe-hover.tsx:37 appears to be a magic number. Consider:

  • Adding a comment explaining why 5px is needed
  • Or making it a named constant: const SAFE_X_OFFSET = 5;

  // Add small offset to prevent hover jitter at element boundaries
  el.style.setProperty("--safe-x", `${e.nativeEvent.offsetX + 5}px`);

---

🐛 Potential Bugs & Issues

No bugs identified. The changes are safe and address the reported issue.

---

⚡ Performance Considerations

• The destructuring of top and bottom is a micro-optimization that reduces getBoundingClientRect() calls from 2 to 1 - good change
• The spread operator ({...props}) has negligible performance impact in React
• Overall performance impact: Neutral to slightly positive

---

🔒 Security Concerns

No security issues identified. The changes are limited to UI interaction logic.

---

🧪 Test Coverage

Recommendation: Consider adding a test to verify that:

1. PrefetchedProjectListItem correctly forwards onHover and onSelect callbacks
2. Hovering over prefetched projects (first 5 items) triggers the onHover callback

This would prevent regression of this bug in the future.

---

📝 Additional Notes

Non-critical formatting changes:

• The JSX reformatting in context-switcher.tsx:274-298 improves readability but isn't strictly necessary for the fix
• The React.ReactNode → ReactNode change in safe-hover.tsx:9 is stylistic

Overall verdict: ✅ Approved - The fix correctly addresses the issue. The suggested improvements are optional enhancements for code clarity.

[graphite-app]

Graphite Automations

"Test" took an action on this PR • (01/08/26)

1 assignee was added to this PR based on Kacper Wojciechowski's automation.