Skip to content

⚡ Bolt: Optimize batch updates to @Published view models#95

Open
acebytes wants to merge 1 commit intomainfrom
bolt/optimize-published-array-mutations-4753550879094667186
Open

⚡ Bolt: Optimize batch updates to @Published view models#95
acebytes wants to merge 1 commit intomainfrom
bolt/optimize-published-array-mutations-4753550879094667186

Conversation

@acebytes
Copy link
Copy Markdown
Contributor

@acebytes acebytes commented Apr 7, 2026

💡 What: Replaced for loop mutations on @Published arrays (scanResults and nodeModulesItems) with functional .map operations that reassign the entire array at once.
🎯 Why: In SwiftUI, mutating an element of an @Published array inside a loop triggers the objectWillChange notification on every single iteration. For lists with many items, actions like "Select All" caused an O(n) avalanche of UI redraws, locking up the main thread.
📊 Impact: Reduces UI invalidation events from O(N) to O(1) for all batch selection operations, significantly improving perceived UI responsiveness.
🔬 Measurement: Can be measured using Instruments (SwiftUI template) while clicking "Select All" on a fully populated node_modules list; the number of View redraws will be drastically lower.


PR created automatically by Jules for task 4753550879094667186 started by @acebytes

Replaced `for` loop mutations in `CacheoutViewModel` with functional `.map` assignments to batch `@Published` updates. This changes the O(n) UI invalidations per operation into O(1), improving SwiftUI responsiveness when interacting with large result lists.

Co-authored-by: acebytes <2820910+acebytes@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant