JohnCosta27/Haystack
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

fix: actually searching properly

Browse Source
This commit is contained in:
John Costa
2025-03-08 15:50:21 +00:00
parent 1bc1b79042
commit 05263d1089
1 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
frontend/src/App.tsx
View File

@ -17,7 +17,7 @@ function App() {
const nav = useNavigate(); const nav = useNavigate();
let fuze = new Fuse<UserImages>([], { keys: ["Text.ImageText"] }); let fuze = new Fuse<NonNullable<UserImages[number]['Text']>[number]>([], { keys: ["Text.ImageText"] });
// TODO: there's probably a better way? // TODO: there's probably a better way?
createEffect(() => { createEffect(() => {
@ -26,13 +26,15 @@ function App() {
return; return;
} }
fuze = new Fuse(userImages, { keys: ["Text.ImageText"] }); const imageText = userImages.flatMap(i => i.Text ?? []);
fuze = new Fuse(imageText, { keys: ["ImageText"], threshold: 0.3 });
}); });
const onInputChange = (query: string) => { const onInputChange = (query: string) => {
// TODO: we can migrate this searching to Rust, so we don't abuse the main thread. // TODO: we can migrate this searching to Rust, so we don't abuse the main thread.
const searched = fuze.search(query).flatMap(s => s.item).flatMap(s => s.Text ?? []); // But, it's not too bad as is.
setSearchResults(searched); setSearchResults(fuze.search(query).flatMap(s => s.item));
} }
return ( return (