Conversation
…to Add New The header search bar only ever searches the library you already have, which is confusing when the book you want isn't added yet — it just shows "No matches". Mirror Sonarr: whenever a term is present, the dropdown now also offers a "Search for '<term>'" affordance that jumps into the Add New metadata search with the term pre-filled and auto-run. - App.vue: add the affordance row in the header search dropdown (shown alongside local matches and in place of the bare "No matches" state), a searchExternally() handler that pushes to the `add-new` route with ?q=<term>, and Enter now falls through to it when there is no local match. - AddNewView.vue: read ?q= on mount and auto-run the search; also watch the query so using the affordance again while already on the page re-runs it. No backend changes; performSearch() already auto-detects the search type. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…n view Two follow-up fixes to the library-search Add New affordance: - When the affordance runs a search while already on /add-new, the results updated further down the page with no viewport change, so it read as a no-op. The query-driven search now scrolls the results into view after running. - The affordance sat after the results inside the max-height:300px scrollable dropdown, so a full list of local matches pushed it out of view entirely — which hid it on the narrow mobile overlay. It's now a sticky footer pinned to the bottom of the dropdown with a solid background, always reachable. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
The header search bar searches the library you already have. When the book you want isn't added yet, it just shows "No matches", with no hint that you should go to Add New — two separate search entry points that are easy to confuse.
This mirrors Sonarr: whenever a term is present, the header dropdown now also offers a "Search for '<term>'" affordance that jumps straight into the Add New metadata search, pre-filled and auto-run.
Behavior
/add-new?q=<term>); the query auto-runs there.Changes
fe/src/App.vue— affordance row + styles in the header dropdown,searchExternally()handler (router.push({ name: 'add-new', query: { q } })), Enter fallthrough.fe/src/views/content/AddNewView.vue— read?q=on mount and auto-run; watchroute.query.qfor subsequent jumps.No backend changes —
performSearch()already auto-detects the search type from the term.Verification
vue-tsctype-check, ESLint, and Prettier all clean on the changed files.Note
Screenshot reference: Sonarr's global search showing an "Add New … / Search for X" item in the same dropdown as existing-library matches — this brings the same escape hatch to Listenarr.
🤖 Generated with Claude Code