⚡ Bolt: Optimize SwiftUI View Model Array Batching#115
Conversation
Changed `for` loops mutaing `.isSelected` properties of array elements in `CacheoutViewModel.swift` to `.map` implementations to batched trigger UI updates instead of causing unnecesary notification looping recalculations. 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: Used functional map to batch updates into single property assignments.
🎯 Why: Mutating elements of
@Publishedarrays inside a loop triggers a UI update notification for every change.📊 Impact: Reduces unnecessary UI recalculations to exactly 1 update per operation instead of O(n).
🔬 Measurement: Verify by observing reduced CPU usage or instrumenting view renders during bulk select operations.
PR created automatically by Jules for task 14290595039862261812 started by @acebytes