feat(landing): add top builders section#334
Conversation
|
@chigozzdevv is attempting to deploy a commit to the Threadflow Team on Vercel. A member of the Team first needs to authorize it. |
|
@chigozzdevv Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
|
Warning Review limit reached
Next review available in: 13 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdds a client-side “Top builders” landing section that fetches leaderboard data, maps contributors into builder cards, handles query states, links to ChangesTop builders landing flow
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
Sequence Diagram(s)sequenceDiagram
participant LandingPage
participant TopBuilders
participant LeaderboardAPI
participant BuilderCard
LandingPage->>TopBuilders: render section
TopBuilders->>LeaderboardAPI: GET /leaderboard?limit=8
LeaderboardAPI-->>TopBuilders: leaderboard entries
TopBuilders->>BuilderCard: render mapped contributors
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |


Summary
apiFetchBuilderCardViewVerification
npm run lintNEXT_PUBLIC_API_URL=https://stage-api.boundlessfi.xyz npm run buildRuntime note
The staging API currently omits
Access-Control-Allow-Originfor the Builders origin. The section handles that request failure, but the backend allowlist must includehttps://builders.boundlessfi.xyzfor live browser data.Closes #320
Summary by CodeRabbit
New Features
Bug Fixes