In terms of not performing what the user might expect from search behaviour, an example I found was the following:
A word "elasticlunr", appears in the linked article, and the linked article appears in search results, but searching any partial string such as "elastic", "elasticl" "elasticlu" and "elasticlun" will not result in finding the linked article. Perhaps this behaviour is intended by the author, but it may not be intended by the various users of the site.
Also the search index has not been updated in 8 months so it doesn't include the several recent articles. Which can be confusing, since those articles are right next to the search box when you're at the homepage. I opened a github issue for him.
The reason is, that I'm working on decoupling the search frontend from the JSON search blobs. Want to make the frontend-part installable through npm as well (and not just cargo as it is now). Didn't get around to adding the search index generation to Github actions yet due to limited time.
Here's the pipeline if you want to give me a hand and add the tinysearch build: https://github.com/mre/mre.github.io/blob/source/.github/wor...
A word "elasticlunr", appears in the linked article, and the linked article appears in search results, but searching any partial string such as "elastic", "elasticl" "elasticlu" and "elasticlun" will not result in finding the linked article. Perhaps this behaviour is intended by the author, but it may not be intended by the various users of the site.
Oddly,
> elastic* and elasticl*
does find the linked article, but
> elasticlu* and elasticlun*
do not.