⚡ Bolt: optimize SecurityAchievementBadges calculations and memoization - #11
Pmaster-dev wants to merge 2 commits into
Conversation
Co-authored-by: Pmaster-dev <293764797+Pmaster-dev@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. |
Co-authored-by: Pmaster-dev <293764797+Pmaster-dev@users.noreply.github.com>
💡 What:
INITIAL_BADGESandCATEGORIESdefinitions outside component scope inclient/src/components/badges/SecurityAchievementBadges.tsx..filter()/.reduce()operations with a single O(N) pass insideuseMemofor category statistics and overall score calculation.useMemoto prevent re-sorting on view mode toggles or parent re-renders.🎯 Why:
On every render (and view toggle), the component previously recreated 23 badge object instances with React JSX elements, and executed 30 array iterations across 10 categories to calculate progress metrics.
📊 Impact:
PR created automatically by Jules for task 3418072675717808566 started by @Pmaster-dev