⚡ Bolt: Optimize redundant filter counts inside useMemo - #94
Conversation
This commit replaces repetitive `.filter(...).length` statements used within JSX loops and top-level hooks across five major files. By consolidating sequential filter passes and map loops into a single `useMemo` `.reduce()` structure, the app minimizes multiple O(N*M) array iterations down to a single O(N) pass, significantly reducing main-thread blocking operations. Co-authored-by: keerthivinod <115292958+keerthivinod@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. |
💡 What:
reduce()hook to accumulate dynamic counts up front rather than iterating with.filter().lengthon every category.page.jsx,DashboardModule.jsx,MaintenanceModule.jsx,ProjectsModule.jsx, andReportsModule.jsx.🎯 Why:
.filter(...).lengthcalculations natively scales poorly when placed within.map()functions inside JSX, causing multiple redundant array traversals on every render.📊 Impact:
useMemohook, ensuring computations only occur when data actually changes.🔬 Measurement:
PR created automatically by Jules for task 1900903139882816463 started by @keerthivinod