Skip to content

fix: don't auto-expand the top group when browsing with no query - #112

Merged
WarlaxZ merged 1 commit into
mainfrom
fix/no-autoexpand-on-browse
Sep 3, 2026
Merged

WarlaxZ merged 1 commit into
mainfrom
fix/no-autoexpand-on-browse

Conversation

@WarlaxZ

@WarlaxZ WarlaxZ commented Sep 3, 2026

Copy link
Copy Markdown
Owner

Summary

  • On the "All" tab in grouped view, submitting an empty search (browsing) popped the top-ranked group open with no query typed and no watch position to justify it.
  • defaultExpandedKeys (src/util/resultGroup.ts) now only falls back to "highest-ranked season" when a real search query was given; a bare browse listing leaves every group closed. This is a shared src/util module, so both the TUI and web grouped views pick up the fix.

Test plan

  • npx vitest run src/util/resultGroup.test.ts — updated existing cases and added coverage for the no-query/no-position browse case
  • npm run lint on changed files
  • Built the app (npm run build) and verified in Chrome: All tab, grouped view, empty search — every group renders closed

🤖 Generated with Claude Code

defaultExpandedKeys fell back to "highest-ranked season" even when
there was no search query and no watch position to seed from — so
landing on the All tab in grouped view with an empty search popped
the top group open for no reason a user could point to. That
fallback now only fires when a real query was typed; a bare browse
listing leaves every group closed.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SDh4YmkPuAoxWtgicYcuJn
@WarlaxZ
WarlaxZ merged commit 7b519a7 into main Sep 3, 2026
6 checks passed
@WarlaxZ
WarlaxZ deleted the fix/no-autoexpand-on-browse branch September 3, 2026 15:03
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.

2 participants