⚡ Bolt: scope lesson progress queries to specific lesson IDs - #102
⚡ Bolt: scope lesson progress queries to specific lesson IDs#102projectamazonph wants to merge 1 commit into
Conversation
Limits the database queries in 'Dashboard', 'Courses' index, and 'Certificate Pending' pages to only fetch progress records matching the retrieved or relevant lesson IDs instead of loading the user's entire historical lesson progress. Co-authored-by: projectamazonph <286085559+projectamazonph@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
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 (3)
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 |
There was a problem hiding this comment.
Pull request overview
This PR reduces unnecessary LessonProgress reads by scoping progress queries to the specific lesson IDs needed by each dashboard surface (dashboard summary, course index progress, and pending-certificate lesson list). This aligns the queried progress set with the lessons actually rendered, cutting down DB payload size and memory use for users with large historical progress.
Changes:
- Dashboard and course index pages now compute published lesson IDs from the fetched course/module/lesson tree and query
lessonProgresswithlessonId: { in: ... }. - Certificate pending-lessons list now limits completed-progress lookup to the lesson IDs being considered.
- Adds empty-ID guards to avoid
in: []queries.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| src/app/(dashboard)/dashboard/page.tsx | Scopes lesson progress lookup to published lesson IDs used on the dashboard. |
| src/app/(dashboard)/courses/page.tsx | Scopes lesson progress lookup to published lesson IDs used on the course catalog index. |
| src/app/(dashboard)/courses/[courseSlug]/certificate/page.tsx | Scopes completed-progress lookup to the course’s lesson IDs used when computing “pending lessons”. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| // Get user's lesson progress (optimized: scope query to published lessons only to avoid loading full history) | ||
| const allPublishedLessonIds = courses.flatMap((c) => | ||
| c.modules.flatMap((m) => m.lessons.map((l) => l.id)) | ||
| ); |
| // Get user's lesson progress (optimized: scope query to published lessons only to avoid loading full history) | ||
| const allPublishedLessonIds = courses.flatMap((c) => | ||
| c.modules.flatMap((m) => m.lessons.map((l) => l.id)) | ||
| ); |
💡 What: Narrows down user lesson progress queries from fetching all progress records globally to strictly filtering by the relevant lesson IDs using Prisma's
inoperator.🎯 Why: For users with many courses or aging accounts, fetching the full historical progress on every dashboard, course list, or pending certificate render generates large unnecessary payloads and high memory consumption.
📊 Impact: Minimizes database response size and network transfer latency, scaling O(1) in the number of lessons in other courses.
🔬 Measurement: Verify query optimization using Prisma query logs or checking that
allPublishedLessonIdsconstraint is applied onlessonId: { in: ... }filter.PR created automatically by Jules for task 7018557561057546950 started by @projectamazonph