Feat: /home caching for logos and startups#49
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe changes refactor the home page architecture from a purely client-side implementation to a hybrid server/client approach, moving data fetching to the server with NocoDB integration and caching. A new Changes
Sequence Diagram(s)sequenceDiagram
participant User as User/Browser
participant Server as Next.js Server
participant NocoDB as NocoDB
participant HomeClient as HomeClient Component
User->>Server: Request /home
activate Server
Server->>NocoDB: Fetch partners (with xc-token)
activate NocoDB
NocoDB-->>Server: Partner records (with filtering by Show, Featured)
deactivate NocoDB
Server->>NocoDB: Fetch startups (with xc-token)
activate NocoDB
NocoDB-->>Server: Startup records (with filtering by Featured/YC/EWOR)
deactivate NocoDB
Server->>Server: Map NocoDB records to Partner[]/Startup[]<br/>(resolve logoUrl, apply fallbacks)
Server->>HomeClient: Render with initialPartners & initialStartups
deactivate Server
HomeClient->>HomeClient: Mount component<br/>(useInView, animated numbers, carousel state)
HomeClient->>User: Deliver HTML + JS
activate User
User->>HomeClient: User interactions<br/>(scroll, carousel navigation, news pagination)
HomeClient->>User: Update UI, animate sections, rotate content
deactivate User
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes Possibly related PRs
Poem
✨ Finishing Touches✨ Simplify code
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 by CodeRabbit
New Features
Bug Fixes
Style
Chores