feat : remove notice search text [no ci]

2026-09-12 16:15:35 +07:00
parent e3c686caed
commit 28a59a8934
9 changed files with 11 additions and 25 deletions
@@ -14,11 +14,11 @@ Use this project’s shared search implementation for finding entities by name o
 - Restrict fuzzy candidates to names, aliases, and individual whitespace-separated words. Keep overview prose and internal keys available for existing direct searches, but exclude them from fuzzy candidates.
 - Normalize with NFC, trim, lowercase, and compare Unicode code points. Keep queries shorter than four code points strict.
 - Use bounded optimal-string-alignment Damerau–Levenshtein distance, including adjacent transpositions. Allow one edit for 4–7 code points and two for longer queries, capped at 25% of query length. Rank by edit distance with stable source-order ties.
- Empty queries return the eligible collection. Show the localized close-match notice only when fuzzy fallback returns results.
+- Empty queries return the eligible collection. Display fuzzy results without an explanatory message.

 ## Reuse the project implementation

-Use `searchItems` from `lib/search.ts`, returning `{ items, fuzzy }`. Supply separate selectors for existing direct-search text and fuzzy candidate names. Use `SearchNotice` from `components/search-notice.tsx` for fallback feedback.
+Use `searchItems` from `lib/search.ts`, returning `{ items, fuzzy }`. Supply separate selectors for existing direct-search text and fuzzy candidate names.

 Use `searchTeams` from `lib/guides/team-search.ts` for collection-level team searches. Apply active groups, permissions, and category restrictions before matching. Explicit DPS sorting takes precedence over fuzzy ranking. Direct team queries must match within one candidate name, not span multiple members.