Skip to content

feat: Introduce Caching (1h valid)#43

Merged
SimonBurmer merged 1 commit intomainfrom
feat/caching
Apr 2, 2026
Merged

feat: Introduce Caching (1h valid)#43
SimonBurmer merged 1 commit intomainfrom
feat/caching

Conversation

@SimonBurmer
Copy link
Copy Markdown
Collaborator

@SimonBurmer SimonBurmer commented Apr 2, 2026

Summary by CodeRabbit

  • Chores
    • Enhanced caching behavior across API endpoints with environment-aware revalidation strategy to improve performance in production environments while ensuring real-time data in development.

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 2, 2026

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

Project Deployment Actions Updated (UTC)
start-munich Error Error Apr 2, 2026 9:59pm

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 2, 2026

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c10d125e-f789-4502-8eda-ceec64cc7cdf

📥 Commits

Reviewing files that changed from the base of the PR and between e7748a3 and b467ed4.

📒 Files selected for processing (8)
  • app/api/board/route.ts
  • app/api/luma/past-events/route.ts
  • app/api/luma/upcoming-events/route.ts
  • app/api/member-network/route.ts
  • app/api/members/batch/[batchId]/route.ts
  • app/api/members/route.ts
  • app/api/partners/route.ts
  • app/api/startups/route.ts

📝 Walkthrough

Walkthrough

Replaced route-level dynamic = 'force-dynamic' caching directives with environment-conditional revalidate configuration across 8 API routes. Updated corresponding fetch requests from cache: 'no-store' to next: { revalidate }, applying 0-second revalidation in development and 3600-second TTL in production environments.

Changes

Cohort / File(s) Summary
Luma Event Routes
app/api/luma/past-events/route.ts, app/api/luma/upcoming-events/route.ts
Transitioned from dynamic = 'force-dynamic' to conditional revalidate configuration and updated fetch caching from cache: 'no-store' to next: { revalidate } with environment-based TTL values.
Member/Network Routes
app/api/member-network/route.ts, app/api/members/route.ts, app/api/members/batch/[batchId]/route.ts
Replaced route-level dynamic forcing with conditional revalidation settings and aligned fetch request caching strategies to use environment-dependent revalidation intervals.
Data Routes
app/api/board/route.ts, app/api/partners/route.ts, app/api/startups/route.ts
Applied consistent caching strategy changes from always-dynamic to ISR-style revalidation with development/production differentiation.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

  • Feat/member network #31: Previously added the app/api/member-network/route.ts file with dynamic = 'force-dynamic' and cache: 'no-store' configuration, which this PR now updates to ISR-style revalidation.

Poem

🐰 Cache strategies hop and bound,
From force-dynamic to revalidation sound,
Dev gets zero, prod gets hours,
ISR unlocks our caching powers!

✨ Finishing Touches
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch feat/caching

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

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

@SimonBurmer SimonBurmer merged commit 8622c38 into main Apr 2, 2026
1 of 3 checks passed
@SimonBurmer SimonBurmer deleted the feat/caching branch April 2, 2026 22:00
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