Replies: 5 comments 2 replies
-
Not sure if this is supported already - don’t think so - but I have a use case where the ability to do incremental indexing would useful. The source files are not all available at a single point in time. Alternatively, the option to merge indexes would work (and actually could be helpful in addition). The use case is a next.js site using static site generation from a mix of local markdown files and other blog posts pulled from a CMS. I’d like to generate a single persisted JSON index file at build time, then run search against it either server side or even client side (TBD). Great library - thank you! |
Beta Was this translation helpful? Give feedback.
-
Thanks for the great library. |
Beta Was this translation helpful? Give feedback.
-
Filtering nested object results. A simple example is only including the properties which are searched. Another example is removing any subarray elements that do not contain any matches, see also #690. |
Beta Was this translation helpful? Give feedback.
-
Hello! Two features I would want for this library:
fuse.search({
$and: [
{
$val: searchTerm,
},
],
})
|
Beta Was this translation helpful? Give feedback.
-
Hi,
regards |
Beta Was this translation helpful? Give feedback.
-
Hey all! Fuse.js has been out for many years, and - dare I say - seems to be the most widely used JS fuzzy search library 😄. For the next iteration of the library, I'd love to know your ideas. What are some things you'd love Fuse.js to handle? Thanks! We can upvote/comment on anything that stands out.
Beta Was this translation helpful? Give feedback.
All reactions