Skip to content

Conversation

@google-labs-jules
Copy link
Contributor

Moved the Translation to UiTranslation mapping from HistoryScreen to HistoryViewModel, running it on a background thread to unblock the UI.


PR created automatically by Jules for task 12837632712009677003 started by @menny

@google-labs-jules
Copy link
Contributor Author

👋 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!


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

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

menny
menny previously approved these changes Jan 5, 2026
@menny menny marked this pull request as ready for review January 5, 2026 15:25
@menny menny force-pushed the bolt-history-optimization-12837632712009677003 branch from 019eb55 to 20127db Compare January 5, 2026 15:30
google-labs-jules bot and others added 3 commits January 9, 2026 10:36
💡 What:
Moved the mapping of `Translation` (DB entity) to `UiTranslation` (UI model) from the UI layer (`HistoryScreen` composable) to `HistoryViewModel`.
This mapping now executes on `Dispatchers.Default` using the `flowOn` operator.

🎯 Why:
Previously, `HistoryScreen` mapped the entire history list on the main thread inside a `remember` block. While `remember` prevents re-execution on every recomposition, the initial calculation and updates blocked the UI thread.
For large history lists, this could cause frame drops.
Moving this to the ViewModel ensures the UI only collects ready-to-render data.

📊 Impact:
Reduces main thread work during history updates.
Simplifies `HistoryScreen` by removing transformation logic.

🔬 Measurement:
Static analysis confirms the mapping is now backgrounded.
Manual verification: Compile and verify type safety.
@menny menny force-pushed the bolt-history-optimization-12837632712009677003 branch from 20127db to 82cdac4 Compare January 9, 2026 16:04
@menny menny merged commit 5d10fb9 into main Jan 9, 2026
1 check passed
@menny menny deleted the bolt-history-optimization-12837632712009677003 branch January 9, 2026 16:08
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