⚡ Bolt: Optimize HistoryGrouper with O(1) loop comparisons #115
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
⚡ Bolt: Optimize HistoryGrouper with O(1) loop comparisons
Optimizes the history grouping logic to improve performance on the history screen.
💡 What:
startOfTodayandstartOfYesterdaytimestamps once outside the loop.Calendaroperations inside the loop with simplelongcomparisons.Calendarallocations.🎯 Why:
HistoryGrouper.groupwas performing repeatedCalendardate math for every item in the history list, which is computationally expensive (O(N * C)).📊 Impact:
🔬 Measurement:
PR created automatically by Jules for task 5838464551610538086 started by @menny