⚡ Bolt: Optimize TimelineView scope in RunningView#218
⚡ Bolt: Optimize TimelineView scope in RunningView#218google-labs-jules[bot] wants to merge 1 commit into
Conversation
…of static elements
|
👋 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: Moved static views (buttons, labels) outside the TimelineView closure in RunningView.
🎯 Why: Wrapping static views in TimelineView forces unnecessary re-evaluation and diffing on every tick.
📊 Impact: Prevents re-rendering static elements every second, saving CPU and battery.
🔬 Measurement: Verify by profiling SwiftUI view updates in Instruments.
PR created automatically by Jules for task 14231159347278177531 started by @TytaniumDev