⚡ Bolt: Batch @Published array updates to prevent UI re-renders#117
⚡ Bolt: Batch @Published array updates to prevent UI re-renders#117
Conversation
Replaced element-by-element mutations of `@Published` arrays (`scanResults` and `nodeModulesItems`) inside `for` loops with batched functional `.map` operations. This prevents severe UI re-render storms triggered by `objectWillChange` firing on every individual element update. 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. |
1 participant
💡 What: Replaced element-by-element mutations of
@Publishedarrays inCacheoutViewModelwith single-assignment functional transformations (.map).🎯 Why: Mutating an element inside a loop triggers a UI update notification for every change, causing unnecessary re-renders.
📊 Impact: Significantly reduces UI recalculations when selecting or deselecting large numbers of items, particularly node_modules.
🔬 Measurement: Observe CPU usage and UI responsiveness when selecting/deselecting all items in a large list.
PR created automatically by Jules for task 16753738394088178501 started by @acebytes