⚡ Bolt: Add stable keys to LazyColumn to optimize Compose re-renders - #5
⚡ Bolt: Add stable keys to LazyColumn to optimize Compose re-renders#5editinghero wants to merge 1 commit into
Conversation
|
👋 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. |
|
Merged locally into main in commit aa1eaae with additional security hardening and biometric cleanup. |
💡 What: Added stable
keyidentifiers toitems(chatMessages),items(filteredHistory), anditems(allNotes)within theAiAssistantBottomSheetcomponent.🎯 Why: Without keys, Jetpack Compose is forced to recompose every item in the
LazyColumnwhen the list changes (e.g., when a new chat message arrives or the user filters history). This causes unnecessary UI churn and jank.📊 Impact: Eliminates O(N) recompositions on list changes, reducing CPU overhead and improving scrolling performance. The UI will now only recompose the specific items that have changed.
🔬 Measurement: Use the Android Studio Layout Inspector or Compose Recomposition counters to observe reduced recomposition counts in the bottom sheet when new chat messages arrive.
PR created automatically by Jules for task 13513607119182896091 started by @editinghero