New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Roadmap #116
Comments
Just started creating a roadmap here thanks to your suggestion.
Not against that, but bundling images into a wasm blob will increase the file-size. If it's just a link to an image, that can be done in the body. tinysearch only uses the body as a corpus of information to match an entry, so it's possible to do that.
Good idea! Can you create an issue for that to track development?
Not sure. Do you have a concrete use-case? Sounds like an advanced feature that not many users might understand or even know it exists. On a technical note, tinysearch is not storing any keywords from the body, just the information if they "exist" - e.g. if they were added to the Bloomfilter before.
Sounds like this could be useful for a shop system or a filter tool. I might be missing something, here. Would like to get the pure search functionality right before thinking about possible extensions. ;)
Yeah, I don't have an idea for a datastructure which stores prefixes without blowing up the wasm binary size. Maybe we can find a neat trick that doesn't consume more storage in the Bloomfilter if searching for a prefix. Keep the ideas coming. 😄 |
Thanks for the feedback, this is also new to me, so just thinking out loud.
As mentioned I was thinking what would be nice to have, not sure how's that gonna work with this project hah Maybe along with 1) if we return additional fields to the frontend we could do additional filtering, even without tinysearh engine. |
Great!
|
Any plans on adding new features?
E.g. adding new fields (like product image),
make body field optional,
adding search filters (e.g. size between/less/bigger than),
booleans (has feature X: yes/no)
or this point in the readme "Only searches for entire words. There are no search suggestions (yet)."
I have no experience building search engines so not really aware what is easy or good idea to build or not.
The text was updated successfully, but these errors were encountered: