Search terms appear to only apply to descriptions, not names

[ian-h-chamberlain]

What happened
Searching for functions by name does not show the function (or functions with similar names) in search results as expected.

Steps to Reproduce
Steps to reproduce the behavior:

1. Perform a search for the name of a function, e.g. optional
2. Suggested function names will be shown as completion suggestions - ignore them and search anyway

Example results page: https://noogle.dev/q?term=optional

Expected behavior
I expected searching for e.g. optional to show lib.optional, lib.optionalAttrs, etc. in results (probably as the first result!), but instead the first results are seemingly unrelated; builtins.path, builtins.fetchGit, etc.

My use case here is a Firefox bookmark keyword for quickly searching from the location bar, using the keyword search feature. In this case I've set https://noogle.dev/q?term=%s as the bookmark URL.

Screenshots

Desktop (please complete the following information):

• OS: macOS Sonoma 14.5 (23F79)
• Browser: Firefox
• Version: 127.0.2
• Screen resolution: 1920x1200

[hsjobeki]

I'll look into it. This happens, because we use "pagefind" and lib.optional is the title, which is relatively unsimilar to optional since it has lib. (4 char, & length is completely different).

I think i should add the name as a h1 title, which has higher weights, but i need to look into the details, how i currently set things up.

I am also open thankfull for any contribution if you want to fix it based on my description.

[ian-h-chamberlain]

Thanks for the quick response! It looks like other users of pagefind have also run into this: Pagefind/pagefind#437

It seems like adding the name as an h1 would work, an alternative might also be to set a custom attribute with a custom weight with data-pagefind-index-attrs.

If I have some time to try out the dev environment I can try to fix it myself! From the README:

Searching within the page is done via pagefind which is only available in the production build.

Is there something special I'll need to do in order to see pagefind-related changes in a local dev environment?

[hsjobeki]

should be fixed with #561

We need some fix for names including ' (prime) it seems that gets tokenized away but it shouldn't.

[ian-h-chamberlain]

@hsjobeki hmm, I tried out the preview deployment from that PR but the results still seem to rank e.g. lib.optional much lower than I'd expect: https://pr-561.noogle.pages.dev/q?term=optional

Is this still something that would only be visible once deployed to prod?

[hsjobeki]

Hey @ian-h-chamberlain sorry for the late reply. Just to let you know i am aware the this issue is still not solved.
I did some research and tried some things today will try to dig a little deeper. It seems there is also an upstream issue with pagefind that exact Matches on the title arent ranked high enough.