🧹 refactor: Extract suggestion logic from CommandBar.svelte - #95
Conversation
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
34dda11 to
0c1c051
Compare
0c1c051 to
c260f60
Compare
🎯 What: Extracted the suggestion logic from
CommandBar.svelteinto a newsuggestions.tsutility file.💡 Why:
CommandBar.sveltewas extremely long and conflated UI markup with complex fuzzy search, filtering, and scoring logic. Extracting this improves readability and allows unit testing the suggestion algorithms without mounting the component.✅ Verification: Ran
bun run checklocally to ensure zero Svelte compilation or typing errors. Re-verified store reactivity by explicitly passing stores ({ browser, tabCounts }) to$:reactive declarations. Verified no unresolved imports.✨ Result: A leaner
CommandBar.sveltefocused purely on UI orchestration. No behavioral changes.PR created automatically by Jules for task 8566463460012556513 started by @undivisible