⚡ Bolt: Batch @Published array updates to reduce UI re-renders#112
⚡ Bolt: Batch @Published array updates to reduce UI re-renders#112
@Published array updates to reduce UI re-renders#112Conversation
Replaces `for` loops with `.map` assignments when mutating arrays within `CacheoutViewModel` to prevent individual elements triggering sequential UI redraw notifications. Co-authored-by: acebytes <2820910+acebytes@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: Replaced
forloops with.mapfunctions when modifying@Publishedcollections (scanResultsandnodeModulesItems) inCacheoutViewModel.🎯 Why: Mutating array elements sequentially within a loop fires standard
@Publishednotifications for every single element, causing massive redundant SwiftUI view recalculations.📊 Impact: Reduces$O(N)$ re-renders to $O(1)$ re-render per batch selection/deselection action, saving significant CPU cycles and maintaining UI responsiveness on large scan lists.
🔬 Measurement: Select all node modules and use Instruments (SwiftUI template) to verify that view recalculations are grouped into a single batch instead of scaling linearly with item count.
PR created automatically by Jules for task 17591344167392478732 started by @acebytes