Skip to content

fix(windows): show the newest kept result after a run drops earlier ones - #4256

Merged
datlechin merged 1 commit into
mainfrom
fix/perf-windows-newest-result
Nov 13, 2026
Merged

datlechin merged 1 commit into
mainfrom
fix/perf-windows-newest-result

Conversation

@datlechin

Copy link
Copy Markdown
Member

Summary

  • After a run past Settings > Queries > Results kept per run, the grid shows the newest kept result, as macOS does. It showed the first kept one.
  • A run under the limit still ends on the result it shows: its first, or the one picked during the run. A picked result the limit kept stays.
  • The choice lives in RunResults.ShownAtEnd; ResultsPane.ShowFirstKept becomes ShowAtEnd. ADR 0004 updated.
  • No changelog fragment: windows/ has none (.claude/rules/changelog.md). No docs change: the docs do not say which result shows.

Test plan

  • App.Model: PastTheLimitADroppedSetShownGivesWayToTheNewestAndAKeptOneStays, ARunWithinTheLimitEndsOnTheSetShown, ARunThatDroppedNothingGivesBackASetOfAnotherRun.
  • UI: ARunPastTheResultLimitKeepsTheNewestAndSaysHowManyWent changes on purpose: the grid shows 4, the newest of the two kept, where it asserted 3, and the picker selects Result 4 (1).
  • This Mac: solution build, solution tests (576 passed). The app and UI tests build and run only in the Windows jobs.

@datlechin
datlechin enabled auto-merge (squash) November 13, 2026 00:41
@datlechin
datlechin merged commit 510d6f2 into main Nov 13, 2026
13 checks passed
@datlechin
datlechin deleted the fix/perf-windows-newest-result branch November 14, 2026 21:29
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