β‘ Bolt: Optimize HistoryGrouper date formatting #121
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.
π‘ What: Optimized
HistoryGrouper.ktto cache month boundaries and formatted strings.π― Why: Iterating through a long history list (sorted by date) was causing redundant
Calendarcalculations andSimpleDateFormatformatting for every single item, even if they belonged to the same month.π Impact: Reduces
CalendarandDateFormatoperations from O(N) to O(M) where M is the number of unique months in the history list. For users with long history, this significantly reduces the CPU time required to group items.π¬ Measurement: Verified with
HistoryGrouperTestwhich includes scenarios for mixed items and boundary conditions. Although direct benchmarks are hard to capture in unit tests, the algorithmic improvement (removing inner loop allocations/calculations) is standard practice for date grouping.PR created automatically by Jules for task 11717478779778066669 started by @menny