-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
Increase Snippet's Truncate number to higher value, or remove that if possible from search.json #401
Comments
Hi @arunshariharan, If you want full text search, you can actually remove the filter In addition, I checked the latest version of Simple-Jekyll-Search. The docs also listed the usage of full-text search. I will upgrade the version of it later. Thanks for your report :) |
@cotes2020 Thanks so much for this! Can't wait for the update to roll out :) Also if I remove the |
Until the next gem release, you can temporarily overwrite the contents of the theme's gem with a file of the same name. See: https://jekyllrb.com/docs/themes/#overriding-theme-defaults |
Thanks so much 😄 |
Checklist
master
branch of the latest code.Is your feature request related to a problem? Please describe
I am writing posts that are longer than 300 words, but the search functionality limits the
snippet
totruncate:300
, which means only 1/3rd of my content in each post is searchable.Describe the solution you'd like
Can we remove the truncate option form
search.json
or increase the limit around1000
?Describe alternatives you've considered
If it is not feasible due to optimization concerns, I was thinking of modifying the search.json locally myself for my build (create assets/js/data/search.json), but unfortunately jekyll does not pickup the changes and replace it while building. I am happy to know if there are any other options to go about it, if changing this is not feasible.
Additional context
The text was updated successfully, but these errors were encountered: