-
Notifications
You must be signed in to change notification settings - Fork 17.6k
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
x/pkgsite: searching for modules isn't supported #36814
Comments
To consider one more related data point, https://pkg.go.dev/search?q=go4.org Perhaps a part of the problem affecting the case described in the original issue is that "sh" is a short word, and so it's hard to use it to find specific results reliability. |
I don't think the short word is related here - like you said, it's just an example. It's also an exact match for the basename of a module path, so the search shouldn't be particularly tricky at all. |
This will be addressed #47321, so closing this issue. |
The current search functionality works on packages alone. That's fine, and useful - but quite limited in the module world.
For example, when I visit https://pkg.go.dev/search?q=sh, I'd expect to see https://pkg.go.dev/mod/mvdan.cc/sh/v3. Particularly since the query string is an exact match with the basename of the module path.
However, because it happens to not be a Go package, it doesn't show up at all as neither a module nor a package. A few sub-packages show up later, but they are scattered, and aren't nearly as useful.
I see two ways this could be addressed:
is:module
. Think like GitHub search, where you can search for both issues and PRs at once, but then trim it down viais:issue
.I think 1 is far better, since most people will just use the default search page, leaving out many of their potentially useful results hidden away.
The text was updated successfully, but these errors were encountered: