5 Commits

Author	SHA1	Message	Date
cjw	27942a2a72	fix(search): stop dropping the name filter for short queries ... The SQL repositories gated the name ILIKE condition on name.len() >= 3 *bytes*, so a 1-2 character search (e.g. "ab") silently returned an arbitrary page of the caller's files instead of matches — while the suggest dropdown (which never had the gate) still found them, making the top-bar search feel broken. The gate existed because the pg_trgm GIN index cannot accelerate sub-trigram patterns, but wrong-but-indexed is never acceptable: caller/folder scoping still bounds the scanned set and result pages are LIMIT-bound. Add a shared name_filter_active() predicate next to like_escape() (any non-blank query filters) and use it at all 7 gate sites — 4 in file_blob_read_repository (condition/bind pairs kept in lockstep so bind indices stay aligned), 3 match guards in folder_db_repository. The Tantivy >= 2 gate on the content index is deliberately left alone: it means "too-short tokens don't enter the full-text index", not a correctness gate. Co-Authored-By: Claude Code <noreply@anthropic.com>	2026-10-01 01:10:39 +08:00
cjw	bd2c7dc45e	refactor(frontend): remove the files-page filter bar; top bar owns filtering ... The top bar's unified search box + filter panel (29d0c335) already drives the same shared filter store, so the files-page SearchFilterBar had become a second, redundant input. Remove the component and its mount; the shared store, URL sync and the files page's in-place search mode all stay — the top bar is now the only filter writer. Drop the orphaned locale keys (filter.placeholder/keyword/clear_keyword) from all 16 locales and rework the affected tests to drive the store directly, with a resetFilters() + URL reset in beforeEach to keep the module-level store from leaking. Co-Authored-By: Claude Code <noreply@anthropic.com>	2026-10-01 01:10:11 +08:00
cjw	deb6dc831b	docs(status): record filter-merge task completion (29d0c335) ... Co-Authored-By: Claude Code <noreply@anthropic.com>	2026-09-27 20:00:03 +08:00
cjw	29d0c33558	feat(frontend): merge top-bar search with the filter bar, expose kind/created filters ... Unify the upstream top-bar search box and the local SearchFilterBar into one filtering capability sharing a single state store, with the URL as its projection: - lib/stores/filter.svelte.ts: module-level $state store, the single source of truth; every surface mutates the same proxy in place - lib/composables/useFilterUrlSync.svelte.ts: one $effect serves both directions (URL -> store adoption, store -> URL replaceState write) with echo suppression so the loop settles in one round-trip - FilterFields.svelte: the five selects (type/size/modified/created/ kind) + recursive switch; word lists and i18n labels live in one place; SearchFilterBar reuses it instead of its own copies - TopBarFilterPanel.svelte: dropdown panel anchored inside the top-bar search input (in-field toggle button with active-count badge); Escape/outside-click close, no overlay stacking with suggestions - FilterChips.svelte: dismissible chips on /search, which is now URL-driven and loses its three inline <select>s - New dimensions the backend already supported: kind (file/folder, resource_types) and created (created_after); URL keys q/type/size/ date/created/kind/recursive, non-defaults only, unknown values degrade to defaults - /files keeps in-place filtering (no navigation); folderTarget carries filter params through folder entry; ?file= and in/scope survive filter writes - topbar.css: input right padding reserves the three in-field controls Backend unchanged. Co-Authored-By: Claude Code <noreply@anthropic.com>	2026-09-27 15:40:20 +08:00
cjw	b7640e9be4	x	2026-09-20 00:28:52 +08:00